At a glance
Workspace
Search
Analytics
Events
Contacts
Companies
Ads Manager
Reports
Segments
Integrations
Health
Diagnostics
Webhooks
AI helpers
The in-app Ask AI chat also gets tools that are not on the public MCP transport:
These are marked internal-only (
external: false) or live only in the in-app agent registry. External MCP clients (Cursor, Claude Desktop, ChatGPT) won’t see them in tools/list.
Tool naming convention
Output format
Most tools acceptformat: "csv" | "json" | "yaml". CSV is the default for tools added in v2.0 because it’s ~50% cheaper in tokens for tabular results. The legacy tools (list_events, list_contacts, query_ad_metrics, etc.) keep json as the default for backwards compatibility — pass format: "csv" explicitly when you want compactness.
Token-budget pagination kicks in around ~6,000 tokens per tool response; when truncation happens the response includes a truncated_at_token_budget: true footer and an opaque next_cursor you should pass back verbatim.
Custom event awareness
Tools that touch custom events —list_events, query_ad_metrics, query_events_aggregated, and friends — automatically rewrite custom_event_* slot ids to your configured labels in their output. You can also pass labels directly:
custom_event_2) on the way in. The result column header comes back as Deal Created, never the internal slug.
Authentication & errors
All external tools authenticate via the OAuth-issued Sanctum token described in Authentication. Errors come back as[error_class] message envelopes — see Rate Limits & Errors for the full taxonomy.