Skip to content

Scopes

Scopes control which tools an API key can call. Each scope follows the pattern {domain}:{action}, where action is read or write. Every tool requires exactly one scope, or none.

The matrix below is generated from the MCP server’s tool catalog on every docs build, so it always matches what the server enforces. Each tool links to its reference entry.

ScopeGrantsTools
workspace:readRead workspaces and workspace-level settingsestimate_cost, get_workspace_memories, get_workspaces
workspace:writeChange workspaces and workspace-level settings; implies onboarding:writecreate_workspace, delete_workspace_memory, edit_workspace, edit_workspace_members, edit_workspace_memory, propose_workspace_playbook_change, refresh_workspace_playbook, submit_feedback
campaigns:readRead campaignsanalyze_company_website, get_campaigns
campaigns:writeChange campaignsedit_campaign
leads:readRead leads and lead-sourcing dataget_companies, get_company_employee_watches, get_lead_comments, get_lead_enrichments, get_lead_refresh_status, get_leads, get_signal_watches
leads:writeChange, import and enrich leadsadd_leads_to_external_destination, delete_company_employee_watch, delete_signal_watch, edit_companies, edit_company_employee_watch, edit_leads, edit_signal_watch, enrich_companies, enrich_leads, import_external_leads, import_leads, lookup_company, refresh_companies, refresh_leads
lead_lists:readRead lead listsget_lead_lists
lead_lists:writeChange lead listsdelete_lead_list, edit_lead_list
workflows:readRead workflows and their activitydiagnose_workflow_sourcing, explain_draft, get_reviews, get_workflow_node_types, get_workflows
workflows:writeChange and run workflowscancel_workflow_node_leads, craft_message, decide_review, delete_workflow, edit_draft, edit_workflow, edit_workflow_graph, recover_review, retry_workflow_entries, trigger_workflow
icps:readLegacy: ICPs are now read through campaignstack_get_campaignsNo current tool
icps:writeLegacy: ICPs are now edited through campaignstack_edit_campaignNo current tool
content:readRead content and craft configurationget_content, get_craft_config_tree, preview_craft_prompt
content:writeChange contentdelete_content, edit_content, edit_identity, refresh_identity_voice
competitors:readRead competitor watchesget_competitor_watches
competitors:writeChange competitor watchesdelete_competitor_watch, edit_competitor_watch
accounts:readRead LinkedIn accountsget_accounts, get_identities
accounts:writeChange LinkedIn accountsconnect_account, edit_account, edit_workspace_accounts, export_linkedin_connections
automations:readLegacy: no current tool requires itNo current tool
automations:writeLegacy: no current tool requires itNo current tool
inbox:readRead the inboxget_conversations
inbox:writeAct in the inbox, including sending messagesedit_conversations, refresh_inbox, send_message
signals:readRead signal agents, watches and job alertsget_exclusions, get_job_applications, get_job_watchers, get_signal_agents, suggest_job_application_profile
signals:writeChange signal agents, watches and job alertsanswer_job_question, apply_to_job, archive_job_watcher, delete_signal_agent, edit_exclusions, edit_job_watcher, edit_signal_agent
integrations:readRead integrationsget_integrations
integrations:writeChange integrations and move leads through themconfigure_integration, edit_workspace_integrations, export_leads_to_crm
notifications:readRead notificationsget_notifications, get_review_time
notifications:writeChange notifications and preferencesedit_notifications, edit_user
outreach:writeSingle LinkedIn actions: connection request, InMail, like, comment, followcomment_on_post, follow_profile, like_post, send_connection_request, send_inmail
google_integrations:readRead calendars and meetingsget_calendar_availability, get_meetings
google_integrations:writeSend email and change calendar events and meetingscancel_meeting, delete_calendar_event, edit_calendar_event, edit_meeting, prepare_meeting_brief, send_email
ads:readLinkedIn Ads (not yet public)No current tool
ads:writeLinkedIn Ads (not yet public)No current tool
seo:readSEO and AI visibility (not yet public)No current tool
seo:writeSEO and AI visibility (not yet public)No current tool
magnets:readRead lead magnetsget_lead_magnets
magnets:writeDiscover and change lead magnetsdiscover_lead_magnets, edit_lead_magnets
proxy:readLegacy: no current tool requires itNo current tool
proxy:writeSet a LinkedIn account’s private proxy (API key only)edit_account_proxy
company_intel:readLegacy: company facts are read through campaignstack_get_companiesNo current tool
company_intel:writeLegacy: company refreshes run through campaignstack_refresh_companiesNo current tool
onboarding:writeFill a new workspace’s self-description (campaignstack_onboard_workspace)onboard_workspace

Tools that need no scope (any valid key can call them): explain_capabilities, get_platform_capabilities, whoami.

Scopes marked Legacy can still be granted to a key, but no current tool requires them. Their tools were folded into broader ones during the V2 consolidation. The ads and seo scopes belong to tools that are not public yet.

write scopes only grant write access; they don’t include read. If an agent needs both (almost always), grant both.

The one implication: workspace:write also grants onboarding:write.

The * scope grants access to all tools. It’s reserved for internal server-to-server connections. API keys always carry an explicit scope list.

Every tool checks its scope before executing. If a key lacks it, the tool returns an error instead of running:

{
"content": [{
"type": "text",
"text": "SCOPE_REQUIRED: \"campaigns:write\" scope is required to call campaignstack_edit_campaign. This API key cannot access it. Use campaignstack_whoami to check your current scopes."
}],
"isError": true
}

campaignstack_whoami needs no scope, so any valid key can call it to see which scopes it holds.