Tool Scopes
The Perspective MCP server supports five named scopes that control which tools are available in a session. By selecting a scope you give the AI assistant a focused tool surface: it can only reach the tools relevant to your current task, which reduces noise and prevents the model from calling irrelevant tools mid-flow.
How to select a scope
Append the scope name to the MCP endpoint path:
POST https://api.perspective.co/mcp/funnel-build
POST https://api.perspective.co/mcp/sequences
POST https://api.perspective.co/mcp/analytics
POST https://api.perspective.co/mcp/crm
Omitting the scope uses all (the default):
POST https://api.perspective.co/mcp
If you pass an unrecognized scope the server returns 400 Bad Request with a list of valid values.
Scope reference
all (default)
Registers every available tool. Use this when you want full access or are exploring what Perspective can do. This is the backward-compatible default for clients that have not migrated to a specific scope.
Tool groups registered: funnels, workspaces, domains, senders, sequences, metrics, sequence-stats, crm, brands
funnel-build
Minimum surface for creating and editing funnels. Excludes metrics, sequences, and CRM tools — those are unreachable, which prevents the model from trying to query stats for a brand-new funnel that has no data yet.
Tool groups registered: funnels, workspaces, domains, brands
Relevant tool pages: Funnels, Workspaces, Brands
sequences
Scoped surface for authoring and managing email sequences.
Tool groups registered: sequences, senders, workspaces, domains
Relevant tool pages: Sequences, Domains & Senders, Workspaces
analytics
Scoped surface for querying metrics and event data. Includes both funnel metrics and sequence performance stats.
Tool groups registered: metrics, sequence-stats, workspaces
Relevant tool pages: Metrics, Sequence Stats, Workspaces
crm
Scoped surface for looking up contacts and CRM properties.
Tool groups registered: crm, workspaces
Relevant tool pages: CRM, Workspaces
Scope → tool group matrix
| Scope | funnels | workspaces | domains | senders | sequences | metrics | sequence-stats | crm | brands |
|---|---|---|---|---|---|---|---|---|---|
all | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
funnel-build | ✓ | ✓ | ✓ | ✓ | |||||
sequences | ✓ | ✓ | ✓ | ✓ | |||||
analytics | ✓ | ✓ | ✓ | ||||||
crm | ✓ | ✓ |
Why scopes matter
Without scopes, every session exposes nearly 30 tools and the model has to decide at each step which one is relevant. When you build a new funnel and the model can also call get_kpi_metrics, it may attempt metric lookups on a funnel with no traffic — wasting tokens on retries. Scopes eliminate this class of error by making irrelevant tools structurally unavailable.
For agents and automated pipelines, always prefer the narrowest scope that covers your workflow.