Skip to main content

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, experiments, workspaces, domains, senders, sequences, metrics, sequence-stats, crm, brands, images, feedback


funnel-build​

End-to-end surface for building a funnel: create and edit it, A/B test it, publish it, and set up the email sequence that follows it. Excludes metrics, sequence stats and contact lookups — those are unreachable, which prevents the model from trying to query stats or contacts for a brand-new funnel that has no data yet.

Tool groups registered: funnels, experiments, workspaces, domains, brands, images, senders, sequences, feedback, and get_crm_properties from crm (the sequence flow needs the contact schema for its trigger and filters)

Relevant tool pages: Funnels, Experiments (A/B Tests), Sequences, Workspaces, Domains & Senders, Brands


sequences​

Scoped surface for authoring and managing email sequences.

Tool groups registered: sequences, senders, workspaces, domains, feedback, and list_funnels from funnels

Relevant tool pages: Sequences, Domains & Senders, Workspaces


analytics​

Scoped surface for querying metrics and event data. Includes funnel metrics, sequence performance stats, and A/B test results. Only the experiment tools that read are included; setting up or changing a test is building, so it lives in funnel-build.

Tool groups registered: metrics, sequence-stats, experiments (read only: get_experiment, list_experiments, get_experiment_results), workspaces, feedback, and list_funnels from funnels

Relevant tool pages: Metrics, Sequence Stats, Experiments (A/B Tests), Workspaces


crm​

Scoped surface for looking up contacts and CRM properties.

Tool groups registered: crm, workspaces, feedback, and list_funnels from funnels

Relevant tool pages: CRM, Workspaces


Scope → tool group matrix​

✓ = the whole group. A tool name = only that tool from the group.

Tool groupallfunnel-buildsequencesanalyticscrm
funnels✓✓list_funnelslist_funnelslist_funnels
experiments: read (get_experiment, list_experiments, get_experiment_results)✓✓✓
experiments: write (create_experiment, update_experiment, end_experiment, discard_experiment)✓✓
workspaces✓✓✓✓✓
domains✓✓✓
senders✓✓✓
sequences✓✓✓
metrics✓✓
sequence-stats✓✓
crm✓get_crm_properties✓
brands✓✓
images✓✓
feedback (send_feedback)✓✓✓✓✓

The experiment tools are only available to accounts with A/B testing enabled. For other accounts, both experiment rows are empty in every scope.

Why scopes matter​

Without scopes, every session exposes more than 40 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.