MCP tool
get_workspace_overview
Read the authenticated brand workspace across every channel and supplier: campaign states, delivery, spend, outcome summaries, freshness and modeled/observed provenance. Supplier names are drill-down dimensions; the brand remains the top-level workspace. Optionally scope the overview to one tenant-owned campaignId.
Input
Pass fields from this schema as the tool arguments. Runtime ownership, product scope and readiness checks still apply.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"from": {
"description": "optional inclusive campaign overlap start, YYYY-MM-DD",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"to": {
"description": "optional inclusive campaign overlap end, YYYY-MM-DD",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"campaignId": {
"description": "optional tenant-scoped campaign id",
"type": "string",
"minLength": 1,
"maxLength": 100
}
}
}REST mapping and authority
The tool wraps this REST endpoint. The mapping identifies path/query/body transformations and approval or idempotency headers.
{
"method": "GET",
"path": "/api/v1/workspace/overview",
"pathFields": [],
"pathSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"pathEncoding": "encodeURIComponent for each path field",
"governedAction": null,
"headers": {},
"querySchema": {
"type": "object",
"properties": {
"from": {
"description": "optional inclusive campaign overlap start, YYYY-MM-DD",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"to": {
"description": "optional inclusive campaign overlap end, YYYY-MM-DD",
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
"campaignId": {
"description": "optional tenant-scoped campaign id",
"type": "string",
"minLength": 1,
"maxLength": 100
}
},
"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.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {},
"additionalProperties": {}
}Safety 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 →