Available tools - Sagepilot Docs

All tools except get_connection_info require a workspace_id argument. Call get_connection_info first, then pass its returned workspace_id into workspace-scoped tools.

Access model

Hosted OAuth connectors request Sagepilot’s full MCP capability set. The connected user’s Sagepilot role and permissions decide which tools can actually use data or make changes. Some MCP hosts may display the full Sagepilot tool list. If the connected user lacks access to a tool, Sagepilot returns an access error when that tool is called. Analytics queries and entity lookup use analytics.query and the selected dataset grant. Journey/campaign configuration tools require their separate product scopes and dataset grants. See Authentication.

Tool	Access	Description
`get_connection_info`	Read	Return MCP session details, resolved workspace ID, and supported datasets.
`get_analytics_catalog`	Read	Discover available analytics metrics, dimensions, and filters.
`query_analytics`	Read	Query tickets, messages, outbound messages, marketing attribution, CSAT, and workforce activity. Supports cursor pagination for marketing attribution.
`search_analytics_entities`	Read	Find campaign or journey IDs by name for analytics filters.
`list_tickets`	Read	List ticket summaries using Sagepilot ticket-list filters; not full-text search.
`unified_search`	Read	Search tickets, messages, customers, and voice calls through unified OpenSearch.
`list_channels`	Read	List connected Sagepilot channels.
`list_agents`	Read	List AI agents and human workspace members.
`export_tickets_csv`	Read	Export ticket rows as CSV, capped for MCP responses.
`support_get_ticket`	Read	Get a support ticket by ID or code.
`support_get_ticket_messages`	Read	Get messages for a support ticket.
`support_search_customers`	Read	Search customers by name, email, phone, or social identifier.
`support_get_customer`	Read	Get a customer by exact ID, email, or phone.
`list_journeys`	Read	List journeys with trigger metadata, per-journey message stats, and status counts.
`get_journey`	Read	Get one journey by ID with a summarized flow graph.
`get_journey_analytics`	Read	Get attributed revenue and estimated ROAS for one journey over a required reporting period.
`list_campaigns`	Read	List campaigns with per-campaign message stats.
`get_campaign`	Read	Get one campaign’s lifetime overview with delivery stats, existing estimated cost, and attribution.
`support_assign_ticket`	Write	Assign a support ticket to an agent, AI agent, team queue, or unassigned state.
`support_update_ticket_status`	Write	Update ticket status and optional sub-status.

Response shape

MCP tools return structured responses with stable fields. This makes the tools easier for AI hosts to inspect, validate, and reuse across follow-up calls. query_analytics and get_journey_analytics share the Analytics API response: dataset, rows, summary, and meta. For marketing attribution, pass a returned meta.cursor into the next call using the same filters and reporting period. Template-category delivery does not support cursors. See Journey and campaign tools for arguments and examples, and Journey and campaign analytics for metric definitions.

​Access model

​Response shape

Access model

Response shape