workspace_id. Call get_connection_info first and use the workspace ID it returns. Replace the example workspace and entity UUIDs with your own.
Choose a tool
Analytics access supports reports and name lookup. Journey/campaign product access is separate. See Authentication for connection permissions.
search_analytics_entities
Find IDs for your analytics filters without fetching journey flows or campaign configuration. The response containsdimension and a members array with value (ID) and label (name), including entities with no activity in the reporting period.
Example arguments for
search_analytics_entities:
value as journey_id or in filters.journey_ids. Campaign results work the same way with campaign_id and filters.campaign_ids. The equivalent REST endpoint is Find entity IDs.
get_journey_analytics
Get attributed revenue and estimated ROAS for one journey over a required reporting period. The tool returns the samedataset, rows, summary, and meta fields as the Analytics API, with attribution_revenue and estimated_roas in each matching row.
Example arguments for
get_journey_analytics:
meta.applied_filters reports the effective workspace settings or overrides. For currency handling, reporting boundaries, and the estimated ROAS formula, see Journey and campaign analytics.
query_analytics
Usequery_analytics with marketing_attribution for date-scoped campaign reports or to compare several journeys and campaigns. Use outbound_messages for delivery rates by template category. Call get_analytics_catalog first to discover supported query shapes.
Example arguments for campaign attribution and estimated ROAS:
workspace_id to the MCP arguments. That page defines the supported dimensions, filters, rates, and category semantics.
Marketing attribution supports cursor pagination; category delivery does not. See Analytics query for the shared request and response contract.
list_journeys
List journey summaries with trigger metadata, per-journey message stats, and status counts. The response also includesattribution_settings and attribution_by_journey_id.
get_journey
Get one journey by ID. The response includes a flow summary with node and edge counts and counts by node type.list_campaigns
List campaign summaries with per-campaign message stats. The response also includesattribution_settings, attribution_by_campaign_id, and voice_stats_by_campaign_id where available.
get_campaign
Get one campaign’s current lifetime overview, including delivery stats, existing estimated cost stats, attribution, retry success count, and voice stats where applicable. The response includestime_scope: "lifetime".
This tool has no reporting-date arguments. For date-scoped campaign attribution or workspace attribution defaults, use query_analytics as shown above.