Skip to main content
This snapshot contains 97 native tool definitions: 47 reads and 50 writes, from source a9c5ee5f196a02b36a6a6764d5999de0668b0c9a (19 October 2026). It describes source capabilities, not a live grant or a claim that all tools have been enabled or executed in every workspace. Follow the connection and permission guide first. Eligible Enterprise owners and administrators choose their permissions through self-service. Current membership, workspace policy, managed plan features, native modules, dependencies and messaging switches filter the actual catalog. Installing or updating a plugin does not expand an existing grant.

How to read the table

  • Scopes in a row are required together unless it explicitly says Any one of.
  • get_price_list accepts any one of products:read, appointments:read or the legacy deals:read alternative. Each scope exposes only its corresponding section; section dependencies and plan features still apply.
  • The plan column records the managed scope feature. Other module and runtime gates may apply even when that column is empty.
  • destructiveHint marks replacement, removal, cancellation or other destructive effects; openWorldHint marks interaction beyond stored workspace records. These are client-facing metadata hints. They do not grant permissions or replace server checks and human approval.
  • Customer sends need a matching send scope and separately enabled sending controls. Confirm mode returns a preview; team-review mode waits for review. Broadcast scheduling always requires confirmation or review.

Tool inventory

create_template requires inbox_id for an existing inbox in the selected workspace. It saves a DRAFT only; submitting a template to Meta or sending it to a customer is a separate operation with additional requirements. Pass components as JSON objects, for example [{"type":"BODY","text":"Your order is ready"}]. When updating a draft, omit components to keep its current content.

Additional output or conditional scopes

The external server does not wire the internal AI-media generation or owner-only ad-publishing adapters. Native MCP elicitation forms are not claimed; ordinary conversation clarification and pending-action confirmation/cancellation are described in the main guide.