tools/list doesn’t advertise them: most are writes and helpers the listed tools reach for you. Use the listed tool unless a result or a tool description names one of these, and fetch the live schema with help_describe first.
agent_cancel
Cancel a running Mode A job by jobId. Aborts the in-process AbortController and, for organic jobs, sends a best-effort HTTP cancel to the agent.
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Cancel a running agent job:
Related:
agent_ask, jobs_status.
Full schema: help_describe {"tool":"agent_cancel"}. As JSON: /mcp/schemas/agent_cancel.json.
jaina_ask
Ask Jaina (regular analyst) a performance/paid-analytics question — ROAS, spend, campaign or ad set/ad performance, pacing, attribution, reporting. Use when the question is about …
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Ask Jaina directly:
Related:
agent_ask, jobs_status, organic_ask.
Full schema: help_describe {"tool":"jaina_ask"}. As JSON: /mcp/schemas/jaina_ask.json.
jaina_pro_run
Run a Jaina Pro long-form report. Returns immediately with { job_id, poll_with } — poll jobs_status for the report (or consume progress frames).
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
A monthly campaign report:
Related:
jobs_status.
Full schema: help_describe {"tool":"jaina_pro_run"}. As JSON: /mcp/schemas/jaina_pro_run.json.
organic_ask
Ask the organic social agent a free-form question about social strategy, captions, hashtags, content ideas, or organic post/account performance. Use when the question is about wha…
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Ask the Organic agent directly:
Related:
agent_ask, jaina_ask, jobs_status.
Full schema: help_describe {"tool":"organic_ask"}. As JSON: /mcp/schemas/organic_ask.json.
insights_get
Fetch Jaina-generated insights for an account, posts, or campaign with cache-first reads.
Actions (
scope):
Other inputs, shared by every action (the live schema says which each action reads):
account_id, target_ids, period, insight_types, refresh.
Examples (IDs are illustrative; use the ones earlier calls return):
Insights for one campaign:
Related:
post_audit.
Full schema: help_describe {"tool":"insights_get","action":"account"}. help_describe’s action takes a scope value. As JSON: /mcp/schemas/insights_get.json.
brand_context_get
Read the active brand’s voice, mission/vision, negative keywords, primary URLs, and taxonomy tags.
Inputs: none.
Examples (IDs are illustrative; use the ones earlier calls return):
Read brand voice + tags:
Related:
brand_profile_get.
Full schema: help_describe {"tool":"brand_context_get"}. As JSON: /mcp/schemas/brand_context_get.json.
brand_profile_get
Read the active brand’s structured profile sections: voice, pmf (product-market fit), audience, and persona. Use section=‘all’ to retrieve everything or specify a single section. …
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Read the brand voice section:
Related:
brand_knowledge, brand_context_get.
Full schema: help_describe {"tool":"brand_profile_get"}. As JSON: /mcp/schemas/brand_profile_get.json.
brand_voice_validate
Brand voice rule checker. Validates copy against the brand’s banned words (the brand DNA’s one list, including brand.md edits), any configured voice_rules (required disclosures, e…
Actions (
platform):
Other inputs, shared by every action (the live schema says which each action reads):
copy.
Examples (IDs are illustrative; use the ones earlier calls return):
Check an Instagram caption:
Related:
brand_knowledge, content_create.
Full schema: help_describe {"tool":"brand_voice_validate","action":"instagram"}. help_describe’s action takes a platform value. As JSON: /mcp/schemas/brand_voice_validate.json.
paid_naming_schema_set
Configure the active brand’s ad-naming convention for a platform: a delimiter (e.g. ’|’) plus an ordered list of field labels (e.g. [‘funnel’, ‘format’, ‘audience’]). Once set, ad…
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Set a Meta naming convention:
Related:
paid_naming_schema_get, paid_manage.
Full schema: help_describe {"tool":"paid_naming_schema_set"}. As JSON: /mcp/schemas/paid_naming_schema_set.json.
intel_audience_push
Push a list of people (emails/phones/names, hashed server-side) to a Meta customer-list Custom Audience — new or appended. Two-phase: mode=‘preview’ (default) → confirm_token; mod…
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
Push HVL audience:
Related:
paid_manage, analytics_cross_platform_spend.
Full schema: help_describe {"tool":"intel_audience_push"}. As JSON: /mcp/schemas/intel_audience_push.json.
mcp_approvals_list
List all pending confirm tokens for the current brand that require admin approval. Returns only tokens where requires.role = ‘admin’. Admin-only.
Inputs: none.
Examples (IDs are illustrative; use the ones earlier calls return):
Changes waiting for an Admin or Owner:
Related:
mcp_approval_grant.
Full schema: help_describe {"tool":"mcp_approvals_list"}. As JSON: /mcp/schemas/mcp_approvals_list.json.
mcp_approval_grant
Grant admin approval for a pending confirm token. The token must have requires.role = ‘admin’. After granting, the token’s approvals array is updated and the originating tool can …
Inputs:
Examples (IDs are illustrative; use the ones earlier calls return):
An Admin or Owner grants a pending change:
Related:
mcp_approvals_list, paid_manage.
Full schema: help_describe {"tool":"mcp_approval_grant"}. As JSON: /mcp/schemas/mcp_approval_grant.json.
What’s next
All tools
Every tool on one page, and the machine-readable index.
Unlisted tools: posts, inbox, and accounts
Tools the server accepts by name but does not list, for Instagram posts, audits, the inbox, connected accounts, and week planning.