MCP tool

get_campaign_insights

One call for the analysis a Head of Data would present to a client: PACING (planned vs delivered to date, and a run-rate projection to flight end), EFFICIENCY (blended and per-channel CPM/CPA plus a weekly trend), OUTCOMES, modeled REACH, the MIX MODEL verdict, INCREMENTALITY, the optimizer RECOMMENDATIONS, and — read this one — LIMITATIONS. Two things are deliberate and must be carried through to whatever you produce. The mix model usually reports status "not-ready" with the weeks it has against the weeks it needs; that refusal IS the finding, not a gap to fill with your own estimate. And `limitations` lists what this analysis cannot claim, derived from the actual data — surface it with the numbers rather than as a footnote, because every line in it is a claim someone would otherwise make by mistake. The projection is a run-rate, not a forecast model.

Input

Pass fields from this schema as the tool arguments. Runtime ownership, product scope and readiness checks still apply.

Input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "campaignId": {
      "type": "string",
      "minLength": 1,
      "description": "campaign id, e.g. cmp-1a2b3c4d"
    }
  },
  "required": [
    "campaignId"
  ]
}

REST mapping and authority

The tool wraps this REST endpoint. The mapping identifies path/query/body transformations and approval or idempotency headers.

Request contract

{
  "method": "GET",
  "path": "/api/v1/campaigns/{campaignId}/insights",
  "pathFields": [
    "campaignId"
  ],
  "pathSchema": {
    "type": "object",
    "properties": {
      "campaignId": {
        "type": "string",
        "minLength": 1,
        "description": "campaign id, e.g. cmp-1a2b3c4d"
      }
    },
    "additionalProperties": false,
    "required": [
      "campaignId"
    ]
  },
  "pathEncoding": "encodeURIComponent for each path field",
  "governedAction": null,
  "headers": {},
  "querySchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "queryEncoding": "URLSearchParams; omit undefined fields, stringify supplied values",
  "responseMapping": "REST JSON is returned as MCP structuredContent and a compatibility text block; privacy-sensitive tools validate their output schema."
}

Output

This is the registered MCP output envelope. Nested fields are only modeled where the schema explicitly defines them.

Output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": {}
}

Safety annotations

MCP annotations

{
  "readOnlyHint": true,
  "destructiveHint": false,
  "idempotentHint": false,
  "openWorldHint": false
}

Annotations help a client present the tool. The API independently enforces authorization and exact action approvals. Error and retry guidance →