MCP tool
get_plan
Fetch a media plan by id: status (draft/approved), line items with budgets and forecasts, total forecast, narrative, and a staleReason if the persona changed since the plan was generated.
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": {
"planId": {
"type": "string",
"description": "plan id"
}
},
"required": [
"planId"
]
}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/plans/{planId}",
"pathFields": [
"planId"
],
"pathSchema": {
"type": "object",
"properties": {
"planId": {
"type": "string",
"description": "plan id"
}
},
"additionalProperties": false,
"required": [
"planId"
]
},
"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": {
"plan": {
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
},
"required": [
"plan"
],
"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 →