Consolidated MCP Tools
Spend less of your agent's context on tool definitions and more on the actual question, with a smaller and more task-shaped set of MCP tools.
What it is
The Amplitude MCP server exposes a smaller set of outcome-based tools rather than one tool per operation. An agent picks a goal, like working with dashboards or cohorts, and passes an action, instead of loading separate tools for each CRUD step.
In internal measurement of the customer-facing tool surface, the upfront tool schema payload dropped by roughly 42%. Workflows that previously took several turns also collapse: dashboards and notebooks accept temporary chart-edit IDs and promote them server-side, so query, save, and insert happen in one call. When an event or property name doesn't resolve, the error returns the closest matching real names instead of asking the agent to go look them up.
Why: Not every MCP client supports dynamic tool search and the excessive context bloat caused due to our server required more end user tokens.
Where: Nothing to configure — the tools change automatically in any MCP client connected to Amplitude. Legacy tool names stop being advertised.
When: GA now