# 360dialog (remote · mcp.360dialog.com)

Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more.

- Trust score: 78/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.360dialog.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-360dialog-mcp/mcp.md), [page](https://verifymcp.io/servers/com-360dialog-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.360dialog.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2.2.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 44/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 20649 tokens (~141/item across 146 items; 138 tools + 8 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 29/100
  - Stability check failed: schema churn in the 13 days we've observed: 17 tool removals, 0 breaking changes, 0 auth/transport breaks, 39 additions.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
  - Structured output schemas are declared (48% of tools); any adoption earns full credit.
- **Tool Safety**: 96/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 18 of 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mba_list_eval_cases" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 140 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the 360dialog MCP server?

360dialog is a hosted endpoint at https://mcp.360dialog.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-360dialog-mcp 'https://mcp.360dialog.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-360dialog-mcp": {
      "url": "https://mcp.360dialog.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-360dialog-mcp": {
      "type": "http",
      "url": "https://mcp.360dialog.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-360dialog-mcp]
url = "https://mcp.360dialog.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-360dialog-mcp": {
      "type": "remote",
      "url": "https://mcp.360dialog.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-360dialog-mcp --url 'https://mcp.360dialog.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-360dialog-mcp:
    url: "https://mcp.360dialog.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-360dialog-mcp": {
      "Transport": "http",
      "Url": "https://mcp.360dialog.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-360dialog-mcp -t streamable-http -u 'https://mcp.360dialog.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-360dialog-mcp": {
      "type": "http",
      "url": "https://mcp.360dialog.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, 0)

- [functional] Server version: 2.2.2 → 2.4.0

### 2026-11-20 (score 78, +1)

- [functional] Server version: 2.2.1 → 2.2.2

### 2026-11-19 (score 77, 0)

- [functional] Server version: 2.0.4 → 2.2.1
- [functional] New tool “mba_get_commerce_settings”
- [functional] New tool “mba_list_catalog_products”
- [functional] New tool “mba_list_product_catalogs”

### 2026-11-18 (score 77, 0)

- [functional] Server version: 2.0.3 → 2.0.4

### 2026-11-17 (score 77, +1)

- [functional] Server version: 2.0.1 → 2.0.3

### 2026-11-16 (score 76, −1)

- [security regression] Stability: 0.23 → fail
- [security regression] Tool “get_balance” was removed
- [security regression] Tool “get_invoices” was removed
- [security regression] Tool “getchat_apply_saved_response” was removed
- [security regression] Tool “getchat_assign_conversation” was removed
- [security regression] Tool “getchat_get_conversation” was removed
- [security regression] Tool “getchat_list_agents” was removed
- [security regression] Tool “getchat_list_conversations” was removed
- [security regression] Tool “getchat_list_groups” was removed
- [security regression] Tool “getchat_list_inboxes” was removed
- [security regression] Tool “getchat_list_saved_responses” was removed
- [security regression] Tool “getchat_list_tags” was removed
- [security regression] Tool “getchat_mark_conversation_as_read” was removed
- [security regression] Tool “getchat_search_conversations” was removed
- [security regression] Tool “getchat_send_message” was removed
- [security regression] Tool “getchat_tag_conversation” was removed
- [security regression] Tool “start_payment_setup” was removed
- [security regression] Tool “test_webhook” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “block_users”, which the server declares destructive
- [security] New tool “change_user_role”, which the server declares destructive
- [security] New tool “create_partner_change_request”, which the server declares destructive
- [security] New tool “enable_local_storage”, which the server declares destructive
- [security] New tool “inbox_apply_saved_response”, which the server declares destructive
- [security] New tool “inbox_assign_conversation”, which the server declares destructive
- [security] New tool “inbox_mark_conversation_as_read”, which the server declares destructive
- [security] New tool “inbox_send_message”, which the server declares destructive
- [security] New tool “inbox_tag_conversation”, which the server declares destructive
- [security] New tool “invite_user”, which the server declares destructive
- [security] New tool “send_test_webhook_event”, which the server declares destructive
- [security] New tool “set_business_username”, which the server declares destructive
- [security] New tool “subscribe_platform_status_updates”, which the server declares destructive
- [security] New tool “unblock_users”, which the server declares destructive
- [security] New tool “unsubscribe_platform_status_updates”, which the server declares destructive
- [security] New tool “update_commerce_settings”, which the server declares destructive
- [security] Tool “get_channel_profile” rewrote its description, which is the text the model reads
- [security] Tool “get_onboarding_status” rewrote its description, which is the text the model reads
- [security] Tool “list_channels” rewrote its description, which is the text the model reads
- [security] Tool “list_users” rewrote its description, which is the text the model reads
- [security] Tool “request_otp” rewrote its description, which is the text the model reads
- [security] Tool “verify_otp” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 17564 → 20075
- [functional improvement] Tool coverage: 41% → 49%
- [functional] New resource “show_channel_list”
- [functional] New resource “show_channel_profile”
- [functional] New resource “show_confirm_action”
- [functional] New resource “show_messaging_analytics”
- [functional] New resource “show_otp_entry”
- [functional] New resource “show_secret_reveal”
- [functional] Server version: 3.4.11 → 2.0.1
- [functional] New tool “get_business_username_suggestions”
- [functional] New tool “get_channel_details”
- [functional] New tool “get_client_details”
- [functional] New tool “get_commerce_settings”
- [functional] New tool “get_currency_migration_status”
- [functional] New tool “get_messaging_analytics”
- [functional] New tool “get_platform_status”
- [functional] New tool “get_voice_analytics”
- [functional] New tool “inbox_get_conversation”
- [functional] New tool “inbox_list_agents”
- [functional] New tool “inbox_list_conversations”
- [functional] New tool “inbox_list_groups”
- [functional] New tool “inbox_list_inboxes”
- [functional] New tool “inbox_list_saved_responses”
- [functional] New tool “inbox_list_tags”
- [functional] New tool “inbox_search_conversations”
- [functional] New tool “list_blocked_users”
- [functional] New tool “list_partner_change_requests”
- [functional] New tool “list_platform_status_subscriptions”
- [functional] New tool “preview_partner_change_request”
- [cosmetic] “list_channels” reworded the description of “size”

### 2026-11-13 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (138)

### `list_skills` (~114 tokens)

List skills

List the 360Dialog skills available to you.

A skill is a curated, up-to-date how-to guide for a 360Dialog process (e.g. drafting a
compliant WhatsApp template, diagnosing a channel that stopped sending). Call this tool
BEFORE answering any "how do I..." question about 360Dialog products or processes -
it tells you which skills exist and when to use them. Once you find a match, call
'get_skill' with its 'name' to read the full guide.

Output parameters:

- `skills` (array)

### `get_skill` (~46 tokens)

Get skill

Get the full guide for one skill returned by 'list_skills', as markdown.

Input parameters:

- `name` (string, required): A skill's 'name' field, as returned by list_skills.

Output parameters:

- `found` (boolean)
- `skill`

### `start_signup` (~38 tokens)

Get 360Dialog signup link

Returns the URL where a user can create a 360Dialog account. Only relevant if the user has not
created a 360Dialog account yet.

Output parameters:

- `next_step` (string)
- `signup_url` (string)

### `search_client_documentation` (~94 tokens)

Search client documentation

Search the 360Dialog client documentation at https://docs.360dialog.com/docs. Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Client Documentation, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

Input parameters:

- `query` (string, required)

### `get_client_documentation_page` (~134 tokens)

Get client documentation page

Get a documentation page from the 360Dialog client documentation at https://docs.360dialog.com/docs. Fetch the full markdown content of a specific documentation page from Client Documentation. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g. https://docs.360dialog.com/docs/getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.

Input parameters:

- `url` (string, required): The URL of the page to fetch

### `get_messaging_analytics` (~202 tokens)

Get messaging analytics

Show messages sent, delivered and billed for a phone number (channel) over a date range, and their cost.

Without dates it covers the last 7 days; ranges over 90 days are summarised by month. Days follow the WhatsApp Business Account's timezone, and today (or this month) appears only once it's over. Rate limited, so prefer one call covering the whole range.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `end_date`: Last day to include, as an ISO date like 2026-05-07. Defaults to today.
- `granularity`: Report by day or by calendar month. Defaults to daily; ranges over 90 days are always monthly.
- `start_date`: First day to include, as an ISO date like 2026-05-01. Defaults to 6 days before the end date, so the last 7 days when no dates are given.

Output parameters:

- `by_category` (array)
- `by_day` (array)
- `channel_id` (string)
- `cost_unavailable` (boolean)
- `currency`
- `current_period_missing` (boolean)
- `display_name`
- `end_date` (string)
- `found` (boolean)
- `granularity` (string)
- `message`
- `phone_number`
- `start_date` (string)
- `timezone`
- `totals`

### `get_voice_analytics` (~173 tokens)

Get voice analytics

Show the number, duration and cost of calls for a phone number (channel) over a date range.

Without dates it covers the last 7 days; ranges over 90 days are summarised by month. Days follow the WhatsApp Business Account's timezone, and today (or this month) appears only once it's over. Rate limited, so prefer one call covering the whole range.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `end_date`: Last day to include, as an ISO date like 2026-05-07. Defaults to today.
- `start_date`: First day to include, as an ISO date like 2026-05-01. Defaults to 6 days before the end date, so the last 7 days when no dates are given.

Output parameters:

- `by_direction` (array)
- `channel_id` (string)
- `cost_unavailable` (boolean)
- `currency`
- `current_period_missing` (boolean)
- `display_name`
- `end_date` (string)
- `found` (boolean)
- `granularity` (string)
- `message`
- `phone_number`
- `start_date` (string)
- `timezone`
- `totals`

### `list_channels` (~202 tokens)

List channels

Find a channel by passing in an identifier.

A channel is a phone number. By calling this tool you retrieve information about the phone number/channel in 360Dialog.

Results are paginated; use the 'page' and 'size' arguments to page through results if there are more than fit in a single page.

Returns:
    If no channel matches, returns "No channels found." If found, returns information of channels, like WABA ID, client ID, channel ID, app ID and the number's 360Dialog Hub page, along with the current page, total pages, and total count.

Input parameters:

- `filter`: Optional filter. You can pass a phone number, client ID, or channel ID here. Defaults to None; call without this argument if you want to get all channels.
- `page` (integer): Page number to retrieve, starting at 1.
- `size` (integer): Number of channels to return per page, at most 100.

Output parameters:

- `channels`
- `found` (boolean)
- `message`
- `page`
- `total_count`
- `total_pages`

### `set_display_name` (~137 tokens)

Set display name

Submit a new display name for this channel (a.k.a. phone number.)

Calling this tool will submit a display name request to Meta. Meta takes up to 48 hours to review the submitted display name. The display name may be rejected if it does not comply with display name guidelines.

The user will receive an email when their display name review is complete.

When this tool is called, the user may be prompted by 360Dialog for an OTP code delivered to their email address.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `new_display_name` (string, required): New requested display name for this phone number.

Output parameters:

- `channel_id` (string)
- `new_display_name` (string)
- `submitted` (boolean)

### `get_channel_profile` (~63 tokens)

Get channel profile

Get a channel's (a.k.a. phone number) WhatsApp profile, and the profile's 360Dialog Hub page.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `project_id` (string, required): Needs to end with 'PR'.

Output parameters:

- `found` (boolean)
- `hub_url`
- `message`
- `profile`

### `update_channel_profile` (~169 tokens)

Update channel profile

Update the WhatsApp profile for this channel (a.k.a. phone number.)

The user may be prompted by 360Dialog for an OTP code delivered to their email address. Make them aware of the OTP requirement.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `new_profile` (object, required): Changes to the business profile. This is a PATCH request, so only pass fields the user wants changed. If you want to clear a field, set it to null. If you don't want to change a field, omit it from t…
- `project_id` (string, required): Needs to end with 'PR'.

Output parameters:

- `channel_id` (string)
- `message` (string)
- `updated` (boolean)

### `get_channel_details` (~139 tokens)

Get channel details

Show the full details of one channel: status, availability, quality rating,
messaging limit, registration code status, and its WABA, project, client and app IDs.

Also shows the channel's WhatsApp Business Account (WABA): its status, Meta business verification status,
message-on-behalf status, phone number and conversation limits, Meta ban state, and any policy violations
affecting this number. Use it to troubleshoot restricted or unverified accounts.

Useful for when the user asks more details for a specific number. Use 'list_channels' to find channels first.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `channel` (object)

### `get_business_username_suggestions` (~53 tokens)

Get business username suggestions

Suggest available WhatsApp business usernames for a channel.

Meta reserves these usernames for the number's business. Use this before 'set_business_username'.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `channel_id` (string)
- `suggestions` (array)

### `set_business_username` (~136 tokens)

Set business username

Claim or change the WhatsApp business username of a channel.

This changes what WhatsApp users see for the business, because the username can be shown instead of the phone number.
Meta may reject the username, in which case an error is returned.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `force_transfer` (boolean): Set to true only if the username is currently on another number of the same business portfolio and should move to this one. Defaults to false.
- `username` (string, required): The username to claim for this number. Use 'get_business_username_suggestions' to see usernames reserved for it.

Output parameters:

- `channel_id` (string)
- `status`
- `username` (string)

### `get_commerce_settings` (~42 tokens)

Get commerce settings

Show whether the WhatsApp Business catalog is visible and the cart is enabled on a channel.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `channel_id` (string)
- `settings` (object)

### `update_commerce_settings` (~120 tokens)

Update commerce settings

Turn the catalog visibility and the cart on or off for a channel.

This changes what WhatsApp users see in the chat with the business. Pass at least one of 'catalog_visible' and
'cart_enabled'; a value that is left out keeps its current setting.

Input parameters:

- `cart_enabled`: Whether the cart is enabled for WhatsApp users. Omit to leave unchanged.
- `catalog_visible`: Whether the catalog is visible to WhatsApp users. Omit to leave unchanged.
- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `channel_id` (string)
- `settings` (object)

### `enable_local_storage` (~79 tokens)

Enable local storage

Store a channel's message data in a chosen region.

The channel is re-registered in Cloud API after calling this tool. Contact our support team
if this tool fails.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `data_localization_region` (string, required): Region code where this number's message data is at rest.

Output parameters:

- `channel_id` (string)
- `data_localization_region` (string)

### `list_blocked_users` (~81 tokens)

List blocked users

Show which WhatsApp users are blocked from messaging a channel.

Meta always returns the BSUID; phone number is only returned when it has been shared with the business.
To unblock a user without a phone number, pass their BSUID to 'unblock_users' in 'user_ids'.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `blocked_users` (array)
- `channel_id` (string)

### `block_users` (~162 tokens)

Block users

Block WhatsApp users from messaging a channel.

Identify each user by phone number or by BSUID; pass at least one of 'phone_numbers' and 'user_ids'.

Only a business can block users who recently messaged it, so some users can fail. The result lists which succeeded and which failed with the reason.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `phone_numbers`: Phone numbers of the WhatsApp users to block, in international format without '+' or spaces, for example ['49100100200'].
- `user_ids`: Business-scoped user IDs (BSUIDs) of the WhatsApp users to block, for users whose phone number isn't known. 'list_blocked_users' shows each blocked user's BSUID.

Output parameters:

- `channel_id` (string)
- `failed` (array)
- `succeeded` (array)

### `unblock_users` (~176 tokens)

Unblock users

Unblock WhatsApp users so they can message a channel again.

Identify each user by phone number or by BSUID; pass at least one of 'phone_numbers' and 'user_ids'.
For a user that 'list_blocked_users' shows without a phone number, pass the BSUID in 'user_ids'.

The result lists which users were unblocked and which failed with the reason.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `phone_numbers`: Phone numbers of the WhatsApp users to unblock, in international format without '+' or spaces, for example ['49100100200'].
- `user_ids`: Business-scoped user IDs (BSUIDs) of the WhatsApp users to unblock, for users whose phone number isn't known. 'list_blocked_users' shows each blocked user's BSUID.

Output parameters:

- `channel_id` (string)
- `failed` (array)
- `succeeded` (array)

### `get_currency_migration_status` (~51 tokens)

Get currency migration status

Show the progress of a WABA's billing currency change.

Returns the most recent migration, or says there is none.

Input parameters:

- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `destination_waba_id`
- `found` (boolean)
- `meta_status`
- `status`
- `target_currency`
- `waba_account_id` (string)

### `wait_for_onboarding_step` (~322 tokens)

Wait for onboarding step

Wait for a server-side onboarding step to finish, then report back.

Embedded Signup and payment setup finish in the person's browser. This tool
polls the hub every 5 seconds for up to 45 seconds and returns one of:

\- "done": The step finished.
\- "pending": Still not finished. Call this tool again to keep waiting.
\- "failed": There was an error.

'channel_id' and 'phone_number' are returned back once a channel is found so you can pass
'phone_number' into the next call once you have it. When 'phone_number' is omitted, 'candidates'
lists the client's most recently created channels - check it if you're unsure the right number
was picked (e.g. two users connecting numbers on the same 360Dialog client account).

Only use this for the short waits during onboarding. This tool is NOT suitable for display name
approval, WABA approval, or business verification scenarios, as they take days, not seconds.

Input parameters:

- `phone_number`: The phone number to wait for - optional. If absent for 'number_connected' and 'channel_live', reports back with top 3 recently connected/went live phone numbers. If present, it checks the status for…
- `step` (string, required): Which step to wait for: 'number_connected' (a new phone number was added), 'payment_connected' (the client has a payment method), or 'channel_live' (the number is ready to send messages).

Output parameters:

- `candidates`
- `channel_id`
- `detail` (string)
- `observed`
- `phone_number`
- `state` (string)

### `get_company_details` (~19 tokens)

Get company details

Get the user's company's details from 360Dialog.

Output parameters:

- `client` (object)

### `update_company_details` (~132 tokens)

Set company details

Set the user's company's details on 360Dialog. This change does not affect Meta; only records on
360Dialog are affected by the update.

Before calling this tool, make sure to:

1\. Check if the `get_company_details` tool returns the correct company information already.
2\. Check with the user if they want to change their company details in 360Dialog.
3\. Get the user's approval/confirmation.

Input parameters:

- `billing_country` (string, required): ISO country code, for example 'DE'
- `company_name` (string, required): The company's name
- `tax_id` (required): Optional - the company's tax ID

Output parameters:

- `client` (object)

### `check_number_eligibility` (~154 tokens)

Check number eligibility

Check whether a phone number can be onboarded for this client before handing over the onboarding link.

This tool only checks 360Dialog's own database and this client's channel quota. It does not ask
WhatsApp/Meta anything, so a number already active on WhatsApp elsewhere (including the personal
app) can still come back eligible here.

Input parameters:

- `check_coex` (boolean): Set to true if the phone number to check is currently on the WhatsApp Business app (not to be confused with the normal, personal, WhatsApp app.) WhatsApp Business app numbers can be onboarded to the…
- `phone_number` (string, required): The phone number to check

Output parameters:

- `checked` (boolean)
- `checks`
- `cta_action`
- `eligibility_status`
- `eligible` (boolean)
- `message`

### `start_number_onboarding` (~150 tokens)

Start number onboarding

Get the link that lets the user connect a WhatsApp phone number in 360Dialog, plus what to tell them beforehand.

This hands over 360Dialog's own onboarding page. The user clicks
through Embedded Signup themselves; this tool cannot do it for them.

The user must be signed in to 360Dialog Hub already, or the link sends them to login first and loses
the destination. Tell them to make sure they're signed in first.

The link given by this tool may not work if the user's 360Dialog client account
is under a partner-paid channel. Make them aware of this.

Returns the client's current channel IDs for future reference on recognizing
which phone number was newly added.

Output parameters:

- `current_channel_ids` (array)
- `onboarding_url` (string)
- `what_meta_will_ask` (array)

### `get_onboarding_status` (~152 tokens)

Get onboarding status

Get a phone number's status on whether a number is live, what type of messages it can send today,
and suggestions for what's next.

A live number can send free-form replies inside the 24-hour customer service window immediately
(meaning if someone messages the number, the user can respond to the message using the API).
Template messages are separately blocked until Meta reviews a submitted template (template reviews
take up to 24 hours.)

Lack of business verification is not a blocker. Unverified businesses can only send 250 templates
to unique users per 24 hours.

Input parameters:

- `channel_id` (required): Needs to end with 'CH'.
- `phone_number`: The phone number of the number being onboarded

Output parameters:

- `availability_status`
- `can_send_templates`
- `channel_status`
- `found` (boolean)
- `live` (boolean)
- `message` (string)
- `messaging_limit`
- `next_step`
- `phone_number`
- `quality_rating`

### `request_otp` (~92 tokens)

Request OTP

Request an OTP code.

Sometimes OTP is needed to complete invoking a tool. When tool invocation fails due to OTP reasons, you will be
notified in the tool response, and be asked to rqeuest an OTP code.

Only call after a tool call fails due to OTP. In clients that show apps, the user enters the code in a card
shown with the result, and the result says so.

Output parameters:

- `expires_at`
- `message` (string)
- `pending_tool`
- `pending_tool_title`
- `requested` (boolean)

### `verify_otp` (~81 tokens)

Verify OTP

Verify the 6-digit OTP code from the user. Doing so will automatically replay the blocked tool call that required
verification, except for tools whose result is shown to the user in an app: for those, the result says to call
the tool again.

Input parameters:

- `code` (string, required): 6-digit OTP code. You must receive this from the user.

Output parameters:

- `call_again_tool`
- `message` (string)
- `replayed` (boolean)
- `replayed_structured_content`
- `replayed_tool`
- `verified` (boolean)

### `get_platform_status` (~46 tokens)

Get platform status

Check whether 360Dialog or WhatsApp currently has an outage or degraded service.

Use this first when messages fail, webhooks stop, or the user asks whether the platform is down.

Output parameters:

- `all_operational` (boolean)
- `components_with_issues` (array)
- `message`
- `pages_with_issues` (array)
- `unavailable_sources` (array)
- `whatsapp_outages` (array)

### `list_platform_status_subscriptions` (~26 tokens)

List platform status subscriptions

List the user's 360Dialog status update subscriptions (delivered via email).

Output parameters:

- `email`
- `message`
- `subscriptions` (array)

### `subscribe_platform_status_updates` (~21 tokens)

Subscribe to platform status updates

Subscribe the user to 360Dialog status update emails.

Output parameters:

- `email`
- `message`
- `subscribed` (boolean)
- `subscriber_id`

### `unsubscribe_platform_status_updates` (~43 tokens)

Unsubscribe from platform status updates

Stop 360Dialog status update emails for the user.

Input parameters:

- `subscriber_id` (string, required): Use 'list_platform_status_subscriptions' to find a subscription's ID.

Output parameters:

- `message`
- `subscriber_id` (string)
- `unsubscribed` (boolean)

### `list_templates` (~117 tokens)

List templates

List templates for a WABA (WhatsApp Business Account). If you do not have a waba_account_id ending in 'WA' (case-insensitive), run the 'list_channels' tool first.

Input parameters:

- `name_filter`: Template name to search for. If one is not provided, leave blank.
- `status_filter`: Filter templates by status. Allowed values are 'approved', 'pending', 'paused', 'rejected'. Leave blank if not needed.
- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `found` (boolean)
- `message`
- `templates`

### `show_template_preview` (~62 tokens)

Show template preview

Show a preview of a given template to the user.

Input parameters:

- `template_id` (string, required): Needs to end with 'WT'. Use 'list_templates' to find a template's ID.
- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `template` (string)

### `get_template_json_example` (~156 tokens)

Get template JSON example

Sending messaging templates in WhatsApp API / 360Dialog API requires a JSON body in the API request.

The API request can be hard to form, as the body must declare in JSON what each parameter in the JSON should
be filled as.

This tool creates a valid example JSON body that the user can later modify before sending the template to WhatsApp users.

It is recommended that you use this tool after creating a template, or after the user asks how to send a template.
Display the JSON result of this tool.

Input parameters:

- `template_id` (string, required): Needs to end with 'WT'. Use 'list_templates' to find a template's ID.
- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `example`
- `message`
- `template_id` (string)
- `template_name` (string)

### `create_template` (~1683 tokens)

Create template

Use this tool to create a WhatsApp message template.

For this tool's 'template_json' property, pass a JSON matching this shape:

{
  "name": string,
  "language": string,
  "category": "MARKETING" | "AUTHENTICATION" | "UTILITY",
  "components": Component[],
}

General rules:
\- name must be lowercase snake_case.
\- category must be uppercase.
\- language must be a WhatsApp locale code such as "en_US", "tr", "es", "pt_BR".
\- Only include fields supported by the component variant.
\- Do not include null fields.
\- Components should normally be ordered as:
  1\. header, if any
  2\. body
  3\. footer, if any
  4\. buttons, if any
\- A template can have at most one header, one body, one footer, and one buttons component.
\- BODY is required unless the user is clearly creating a special authentication template handled elsewhere.
\- HEADER and FOOTER are optional.
\- BUTTONS are optional.

Component variants:

1\. Text header without variables

{
  "type": "HEADER",
  "format": "text",
  "text": "Your order update"
}

Use this when the header is plain text.

2\. Text header with variables

{
  "type": "HEADER",
  "format": "TEXT",
  "text": "Hi {{1}}",
  "example": {
    "header_text": ["Alice"]
  }
}

Rules:
\- Text header supports template variables.
\- If text contains variables, include example.header_text.
\- The example array must contain sample values in the same order as the variables appear.
\- For named parameters, the placeholder names appear in text, but the examples are still values.

3\. Image header

{
  "type": "HEADER",
  "format": "IMAGE",
  "example": {
    "header_handle": ["https://example.com/sample-image.jpg"]
  }
}

Use this when the template header should contain an image.
The example should be a sample image handle or URL when available.

4\. Video header

{
  "type": "HEADER",
  "format": "VIDEO",
  "example": {
    "header_handle": ["https://example.com/sample-video.mp4"]
  }
}

Use this when the template header should contain a video.
The example should be a sam…

Input parameters:

- `template_json` (object, required): The template's JSON.
- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `created` (boolean)
- `example`
- `message`
- `template`

### `delete_template` (~62 tokens)

Delete template

Delete a WhatsApp message template by its internal template ID.

Input parameters:

- `template_id` (string, required): Needs to end with 'WT'. Use 'list_templates' to find a template's ID.
- `waba_account_id` (string, required): Needs to end with 'WA'.

Output parameters:

- `deleted` (boolean)
- `message` (string)
- `template_id` (string)

### `get_webhook` (~185 tokens)

Get webhook

Get a channel's (a.k.a. phone number's) webhook URL, and check if the optional webhook headers are set.

Webhook headers are optional. They can be set using the 'set_webhook' tool, which also sets the webhook URL.
When webhook headers are set, 360Dialog will send webhooks to the channel's webhook URL and add the specified headers.

This helps only authenticated requests pass through app firewalls, if the user has any.

Example:

If webhook URL is `https://foo.com/webhook`, and webhook headers are set to {"x-360dialog-webhook-security": "RANDOM-STRING"},
the webhook URL will receive POST requests like this:

POST https://foo.com/webhook
HEADERS
    x-360dialog-webhook-security: RANDOM-STRING

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.

Output parameters:

- `configured` (boolean)
- `masked_headers` (object)
- `message`
- `webhook`

### `set_webhook` (~51 tokens)

Set webhook

Set a channel's (a.k.a. phone number's) webhook URL and optionally webhook headers.

Input parameters:

- `channel_id` (string, required): Needs to end with 'CH'.
- `webhook_setting` (object, required)

Output parameters:

- `configured` (boolean)
- `message`
- `webhook`

### `send_test_webhook_event` (~151 tokens)

Send test webhook event

Send sample events to a channel's (a.k.a. phone number's) or a WABA's webhook, so the user can
check that the webhook receives them and answers with a 2xx code.

Pass exactly one of 'channel_id' or 'waba_account_id'. The user may see several sample requests arrive at
their webhook server. Returns which sample events passed and which failed.

Input parameters:

- `channel_id`: Channel ID, ending in 'CH', to test that channel's webhook. Leave blank when testing a WABA.
- `waba_account_id`: WABA ID, ending in 'WA', to test the WABA's webhook. Leave blank when testing a channel.

Output parameters:

- `failed_count` (integer)
- `message` (string)
- `passed_count` (integer)
- `results` (array)
- `sent` (boolean)
- `target` (string)
- `target_id` (string)

### `get_self` (~49 tokens)

Get current user

Get currently logged in user's information in 360Dialog. You will get:
\- user's name,
\- user's email address,
\- partner name,
\- user's permissions in 360Dialog Hub,
\- user's roles

Output parameters:

- `audience` (string)
- `message`
- `ok` (boolean)
- `profile`

### `list_users` (~42 tokens)

List users

List users of the selected account, including their roles and creation timestamps.

Client users get the users of their own client account, partner users the users of the partner account.

Output parameters:

- `message`
- `ok` (boolean)
- `users`

### `invite_user` (~177 tokens)

Invite user

Invite a new user to the account, with a role. The invitee gets an email with a link to set their password.

Client users invite to their own client account, partner users to the partner account. To create a new client
together with its first user, use 'create_client_and_invite'.

The user may be prompted by 360Dialog for an OTP code delivered to their email address.

Input parameters:

- `email` (string, required): Email address of the person to invite.
- `name` (string, required): Full name of the person to invite.
- `role` (string, required): Role to give the new user. 'partner-owner' or 'partner-member' on a partner account, 'client-owner' or 'client-member' on a client account. Owners can invite users and manage the account; members can…

Output parameters:

- `account` (string)
- `email` (string)
- `invited` (boolean)
- `message` (string)
- `role` (string)

### `change_user_role` (~126 tokens)

Change user role

Change the role of an existing user of the account. Users cannot change their own role.

Client users change users of their own client account, partner users users of the partner account.

The user may be prompted by 360Dialog for an OTP code delivered to their email address.

Input parameters:

- `role` (string, required): New role. 'partner-owner' or 'partner-member' on a partner account, 'client-owner' or 'client-member' on a client account.
- `user_id` (string, required): Needs to end with 'U'. Use 'list_users' to find a user's ID.

Output parameters:

- `account` (string)
- `changed` (boolean)
- `message` (string)
- `role` (string)
- `user_id` (string)

### `sandbox_register_number` (~99 tokens)

(Sandbox) Register number

Register the user's phone number on the 360Dialog sandbox. Upon registration, the user can send messages to this phone number from the 360Dialog sandbox account on WhatsApp.

The user will be given a link to complete registration. When this link is used, they will send a verification code to 360Dialog sandbox phone number on WhatsApp. They can click the link, or alternatively scan the QR code.

Input parameters:

- `phone_number` (string, required)

Output parameters:

- `message_to_send` (string)
- `quick_link` (string)
- `sandbox_number` (string)

### `sandbox_complete_registration` (~43 tokens)

(Sandbox) Complete registration

Complete a phone number's registration. This will get you the API key to use when sending messages from the 360Dialog sandbox phone number to the user's registered phone number.

Output parameters:

- `api_key` (string)
- `mdn` (string)
- `messages_left` (integer)

### `sandbox_send_message` (~348 tokens)

(Sandbox) Send message

Send a message on the 360Dialog sandbox. Messages can only be sent to the user's phone number that was used during sandbox registration.

The payload must be a JSON string matching the WhatsApp messages endpoint body.

Interactive message example: use this only when there is an active conversation window, which lasts 24 hours since the customer's last message.

{
  "messaging_product": "whatsapp",
  "to": "{{recipient_phone_number}}",
  "type": "text",
  "text": {
    "body": "{{message_body}}"
  }
}

Template message example: use this when there is no active conversation window, or when sending an approved template message. You can only send the 'marketing_message' template.

{
  "messaging_product": "whatsapp",
  "to": "{{recipient_phone_number}}",
  "type": "template",
  "template": {
    "name": "marketing_message",
    "language": {
      "policy": "deterministic",
      "code": "en"
    },
    "components": [
      {
        "type": "header",
        "parameters": [
          {
            "type": "image",
            "image": {
              "link": "https://placehold.co/600x315/34D399/FFFFFF/png?text=Summer+Sale!"
            }
          }
        ]
      }
    ]
  }
}

Input parameters:

- `api_key` (string, required): Sandbox API key
- `payload` (string, required): JSON body of the WhatsApp message to send. Use a text payload only inside an active 24-hour customer service window; use a template payload to start or continue conversations outside that window.

Output parameters:

- `contacts` (array)
- `messages` (array)
- `messaging_product` (string)

### `sandbox_configure_webhook` (~51 tokens)

(Sandbox) Configure webhook

Set webhook for the channel on 360Dialog sandbox. Optional.

Input parameters:

- `api_key` (string, required): Sandbox API key
- `url` (object, required): Webhook to set for this channel on sandbox

Output parameters:

- `headers`
- `url`

### `sandbox_get_webhook_configuration` (~34 tokens)

(Sandbox) Get webhook configuration

Get configured webhook for the channel on 360Dialog sandbox.

Input parameters:

- `api_key` (string, required): Sandbox API key

Output parameters:

- `headers`
- `url`

### `sandbox_list_events` (~53 tokens)

(Sandbox) List events

List webhook events received. This will show received messages from the user, and status of messages
sent from the sandbox account.

Input parameters:

- `page` (integer): Page number. Starts from 1, defaults to 1.

Output parameters:

- `items` (array)
- `page` (integer)
- `pages` (integer)
- `size` (integer)
- `total` (integer)

### `get_client_details` (~50 tokens)

Get client details

Show one client's account details and status: name, status, number limit, contact information and Meta
business ID.

Client users see their own account. Partner users pass the ID of one of their clients.

Output parameters:

- `client`
- `found` (boolean)
- `message`

### `list_partner_change_requests` (~153 tokens)

List partner change requests

List requests to move numbers between partners, with their status.

Client users see the requests their client made. Partner users see the requests addressed to their partner,
which they can approve or reject; a partner can pass 'client_id' to only see the requests of one client.
Pass 'request_id' to follow the status of one request.

Input parameters:

- `page` (integer): Page number to retrieve, starting at 1.
- `request_id`: Optional. Only show the request with this ID.
- `size` (integer): Number of requests to return per page, at most 100.
- `status`: Optional. Only list requests in this status. 'created' means waiting for the new partner's approval.

Output parameters:

- `count` (integer)
- `message` (string)
- `requests` (array)
- `total`

### `preview_partner_change_request` (~241 tokens)

Preview partner change request

Check whether numbers can move to a new partner, without creating a request. Runs the same pre-flight checks
as 'create_partner_change_request' and reports every issue that would block the move (for example a number
that cannot move, a missing company detail, or a request that is already in progress).

Nothing is created or changed. Show the result to the user, then, if it is clear, call
'create_partner_change_request' with the same arguments.

Input parameters:

- `channel_bundles`: Optional. Which payment plan of the new partner each number moves onto. Only needed when the new partner bills its clients.
- `channel_ids` (array, required): IDs of the numbers (channels) to move. Use 'list_channels' to find them. All numbers of a WABA have to move together.
- `target_client_id`: Optional. ID of an existing client at the new partner to move the numbers into. Only for a partial move (not all numbers of the client). Needs to end with 'CL'.
- `target_partner_id` (string, required): ID of the partner the numbers should move to. Needs to end with 'PA'.

Output parameters:

- `actions_required` (array)
- `message` (string)
- `ready` (boolean)

### `create_partner_change_request` (~260 tokens)

Create partner change request

Request that the client's numbers move to a new partner. The new partner has to approve the request; then the
numbers are moved, which changes who manages them and who is billed.

ALWAYS call 'preview_partner_change_request' first with the same arguments, show its result to the user and
get their confirmation before calling this tool. This tool also runs the preview itself and does NOT create the
request when the preview finds issues; it then returns the issues instead.

The user may be prompted by 360Dialog for an OTP code delivered to their email address.

Input parameters:

- `channel_bundles`: Optional. Which payment plan of the new partner each number moves onto. Only needed when the new partner bills its clients.
- `channel_ids` (array, required): IDs of the numbers (channels) to move. Use 'list_channels' to find them. All numbers of a WABA have to move together.
- `target_client_id`: Optional. ID of an existing client at the new partner to move the numbers into. Only for a partial move (not all numbers of the client). Needs to end with 'CL'.
- `target_partner_id` (string, required): ID of the partner the numbers should move to. Needs to end with 'PA'.

Output parameters:

- `actions_required` (array)
- `created` (boolean)
- `message` (string)
- `preview_ready` (boolean)
- `request`

### `inbox_send_message` (~248 tokens)

Send message

Send a message into an existing conversation, as the business.

This is inbox-scoped sending: it posts into an existing conversation with
correct threading. Outside the 24-hour customer-care window, WhatsApp only
permits template messages — other types are rejected with an explanation.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `content`: The type-specific message object, following the WhatsApp Business API shape. For type=text: {"body": "..."}. For image/video: {"link": "https://...", "caption"?}. For document: {"link": "https://..."…
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `type` (string): WhatsApp message type of `content`.

### `inbox_assign_conversation` (~172 tokens)

Assign conversation

Assign or reassign one conversation to an agent and/or a group.

Both fields are always set to exactly what you pass: calling with only
\`user_id` clears any group assignment and vice versa; calling with neither
unassigns the conversation entirely.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `group_id`: Group ID from list_groups to assign; omit/null to leave unassigned.
- `user_id`: Agent (user) ID from list_agents to assign; omit/null to leave unassigned.

### `inbox_tag_conversation` (~116 tokens)

Tag conversation

Add or remove one tag on one conversation.

Input parameters:

- `action` (string): Add the tag to or remove it from the conversation.
- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `tag_id` (integer, required): Tag ID from list_tags.

### `inbox_mark_conversation_as_read` (~234 tokens)

Mark conversation as read

Mark one conversation's messages as read by the calling user.

Pass `up_to_timestamp` after reviewing a conversation so that messages
arriving in the meantime stay unread. The read mark only moves forward: a
timestamp older than the caller's current mark changes nothing. Read state
is per inbox user: this clears the unread count for the caller only, not
for other agents. The inbox also marks the messages as read on WhatsApp,
so the contact sees read receipts. Only conversations whose messages you
can read can be marked.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `up_to_timestamp`: Timestamp of the last message you reviewed, taken from get_conversation results; messages up to and including it are marked read, newer ones stay unread. Omit to mark everything currently in the conv…

### `inbox_apply_saved_response` (~124 tokens)

Apply saved response

Send a saved (canned) response into a conversation as a text message.

Subject to the same 24-hour window rule as inbox_send_message.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `saved_response_id` (integer, required): Saved response ID from list_saved_responses.

### `inbox_list_conversations` (~126 tokens)

List conversations

List conversations of the inbox, newest activity first.

Returns one entry per conversation with contact info, unread count, last
message, current assignee (user and/or group), and tags.

Input parameters:

- `assigned_to_me` (boolean): Only conversations assigned to the calling user.
- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `limit` (integer)
- `offset` (integer)
- `tag_id`: Only conversations carrying this tag (see list_tags).
- `unread` (boolean): Only conversations with unread incoming messages.

### `inbox_search_conversations` (~108 tokens)

Search conversations

Find conversations by contact name, phone number, tag name, or message content.

Searches contact profiles and tags first, then message text and media
captions; results from both are merged and deduplicated by conversation.
Each match notes why it matched (`contact` or `message_content`).

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `limit` (integer)
- `query` (string, required): Text to search for.

### `inbox_get_conversation` (~169 tokens)

Get conversation

Read one conversation: contact/assignment/tag details plus its message history.

Messages are returned newest first. To page further back, call again with
\`before_time` set to the oldest returned message's timestamp.

Input parameters:

- `before_time`: Only messages strictly older than this POSIX timestamp — use for paging back through history.
- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `conversation_id` (string, required): The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it.
- `limit` (integer): Maximum number of messages to return.
- `since_time`: Only messages at or after this POSIX timestamp.

### `inbox_list_inboxes` (~156 tokens)

List inboxes

List the WhatsApp inboxes the calling 360dialog user can access.

Call this first when you don't know which `channel_id` to pass to the
other tools: each entry pairs a `channel_id` with its inbox URL and
WhatsApp number (`wa_id`). Entries without a `channel_id` cannot be
driven through these tools.

The listing covers the caller's own client accounts, plus every inbox under
a partner the caller administers. It never reaches another tenant: a client
user is not shown other clients' inboxes, including ones managed by the same
partner. An empty list does not mean no inbox exists; pass a known
\`channel_id` to the other tools directly.

### `inbox_list_agents` (~61 tokens)

List agents

List the inbox's agents (users) — for assignment via inbox_assign_conversation.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `is_available`: Filter by availability; omit to list all agents.

### `inbox_list_groups` (~45 tokens)

List agent groups

List the inbox's agent groups — for group assignment via inbox_assign_conversation.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.

### `inbox_list_tags` (~50 tokens)

List tags

List the inbox's tags — for tagging via inbox_tag_conversation and filtering via inbox_list_conversations.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.

### `inbox_list_saved_responses` (~63 tokens)

List saved responses

List the inbox's saved (canned) responses — for use with inbox_apply_saved_response.

Input parameters:

- `channel_id` (string, required): The 360dialog channel ID of the inbox to operate on.
- `search`: Only saved responses whose text contains this substring.

### `mba_check_agent_eligibility` (~108 tokens)

Check agent eligibility

Check whether this channel's WhatsApp number is eligible for a Meta Business Agent. Returns {is_eligible: boolean}. Known limitation: a 403 from this call can mean the number is simply not eligible, rather than that the business has not accepted Meta's terms - do not report an unaccepted-terms problem on a 403 alone.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_onboard_agent` (~109 tokens)

Onboard the agent

Create the Meta Business Agent for this channel on the given messaging channel. Creates the underlying entities and schedules asynchronous data-preparation jobs, so the agent is not immediately ready to answer. Returns {agent_id}. Onboarding does not switch the agent on: rollout stays disabled until mba_update_agent_settings enables it.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `channel` (string, required): Messaging channel to onboard.

### `mba_delete_agent` (~104 tokens)

Delete the agent

Remove the Meta Business Agent from this channel's WhatsApp number. Deletes the agent configuration and, when the last agent on the account is removed, disconnects the integration entirely. Returns {deleted_agent_id}. This is irreversible: knowledge, skills and connectors configured on the agent go with it, and restoring the setup means onboarding again from scratch.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_get_agent_settings` (~115 tokens)

Read agent settings

Read the agent's current settings: rollout, handoff, followup and ai_audience. Known limitation: this returns an ARRAY with one entry per channel, not a single object. Read the entry whose `channel` you care about (usually "whatsapp") rather than treating the response as an object.

Input parameters:

- `agent_id` (string): Optional - restrict the read to one agent.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_update_agent_settings` (~222 tokens)

Update agent settings

Replace the agent's settings and return the updated entry. Known limitation: this is a FULL REPLACEMENT, not a patch - every field you omit is reset, so read the current settings with mba_get_agent_settings first and send them back with your change applied. Note also that setting rollout.enabled to false stops the AI responding on all threads; re-enabling it makes the AI respond to new threads only, not to threads that were already open.

Input parameters:

- `agent_id` (string): Optional - restrict the update to one agent.
- `ai_audience` (string): ALLOWLISTED_ONLY restricts the agent to the numbers on the allowlist.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `followup` (object): Following up with an inactive user.
- `handoff` (object): Handing the conversation to a human agent.
- `rollout` (object): Whether the agent responds at all. Disabling it stops the AI answering on every thread.

### `mba_list_allowlist_entries` (~86 tokens)

List allowlisted numbers

List the consumer phone numbers allowed to reach the agent while ai_audience is ALLOWLISTED_ONLY. Known limitation: this returns a BARE ARRAY of {id, consumer_phone_number}, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_add_allowlist_entry` (~116 tokens)

Add an allowlisted number

Add one consumer phone number to the allowlist. Returns the created {id, consumer_phone_number}. The allowlist only takes effect while ai_audience is ALLOWLISTED_ONLY; under EVERYONE the agent answers all consumers regardless of this list.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `consumer_phone_number` (string, required): Consumer's WhatsApp number in E.164 format, e.g. +15551234567.

### `mba_remove_allowlist_entry` (~113 tokens)

Remove an allowlisted number

Remove one entry from the allowlist by its entry id, which comes from mba_list_allowlist_entries (it is not the phone number). Returns no content on success. While ai_audience is ALLOWLISTED_ONLY, removing the entry stops the agent answering that consumer.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `entry_id` (string, required): Allowlist entry id, as returned by list_allowlist_entries.

### `mba_get_business_info` (~148 tokens)

Read business info

Read the business information the agent uses to answer customers. Returns empty or default values when none has been configured. Known limitation: business info is a CLOSED six-field schema - business_description, contact_info, delivery_and_shipping, payment_method, purchase_info, return_policy. Any other key is rejected. Knowledge that does not fit one of these six fields belongs in an FAQ (mba_create_faq), an agent skill (mba_create_agent_skill), a crawled website (mba_create_website) or an uploaded file (mba_upload_file) - not here.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_update_business_info` (~243 tokens)

Update business info

Replace the agent's business information and return the stored object. Known limitation: this is a FULL REPLACEMENT - fields you omit are cleared, so read mba_get_business_info first and send the existing values back with your change applied. Known limitation: business info is a CLOSED six-field schema - business_description, contact_info, delivery_and_shipping, payment_method, purchase_info, return_policy. Any other key is rejected. Knowledge that does not fit one of these six fields belongs in an FAQ (mba_create_faq), an agent skill (mba_create_agent_skill), a crawled website (mba_create_website) or an uploaded file (mba_upload_file) - not here.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `business_description` (string): What the business does.
- `contact_info` (object): Contact and location details.
- `delivery_and_shipping` (string): Delivery and shipping terms.
- `payment_method` (string): Accepted payment methods.
- `purchase_info` (string): How customers buy.
- `return_policy` (string): Returns and refunds.

### `mba_reset_business_info` (~162 tokens)

Reset business info

Reset the agent's business information to empty defaults and return the emptied object. Unlike most deletes this does not 404 afterwards - mba_get_business_info keeps working and returns the defaults. Known limitation: business info is a CLOSED six-field schema - business_description, contact_info, delivery_and_shipping, payment_method, purchase_info, return_policy. Any other key is rejected. Knowledge that does not fit one of these six fields belongs in an FAQ (mba_create_faq), an agent skill (mba_create_agent_skill), a crawled website (mba_create_website) or an uploaded file (mba_upload_file) - not here.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_list_faqs` (~65 tokens)

List FAQs

List the agent's FAQ entries. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_create_faq` (~108 tokens)

Create an FAQ

Add one question-and-answer entry to the agent's knowledge. Returns the created entry with its id. FAQs are the right home for knowledge that does not fit business info's six fields.

Input parameters:

- `answer` (string, required): The answer the agent should give.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `metadata` (object): Optional free-form metadata.
- `question` (string, required): The customer's question.

### `mba_get_faq` (~70 tokens)

Read an FAQ

Read one FAQ entry by its id, as returned by mba_list_faqs or mba_create_faq.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `faq_id` (string, required): FAQ entry id.

### `mba_update_faq` (~111 tokens)

Update an FAQ

Replace one FAQ entry by its id. Both question and answer are required: this replaces the entry rather than patching it, so send the fields you want the entry to end up with.

Input parameters:

- `answer` (string, required)
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `faq_id` (string, required): FAQ entry id.
- `metadata` (object): Optional free-form metadata.
- `question` (string, required)

### `mba_delete_faq` (~62 tokens)

Delete an FAQ

Delete one FAQ entry by its id. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `faq_id` (string, required): FAQ entry id.

### `mba_list_websites` (~72 tokens)

List crawled websites

List the websites the agent crawls for knowledge, with their crawl status. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_create_website` (~93 tokens)

Add a website to crawl

Add a website URL for the agent to crawl into its knowledge base. Returns the entry with its id and crawl status. Crawling is asynchronous - the knowledge is not available immediately; poll mba_get_website for crawl_status.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `url` (string, required): Website URL to crawl.

### `mba_get_website` (~92 tokens)

Read a crawled website

Read one website crawl entry by its id, including crawl_status, pages_crawled and last_crawled_at. This is how you check whether a site added with mba_create_website has been ingested yet.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `website_id` (string, required): Website entry id.

### `mba_update_website` (~71 tokens)

Update a crawled website

Replace the URL of one website crawl entry. Changing the URL restarts crawling.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `url` (string, required)
- `website_id` (string, required): Website entry id.

### `mba_delete_website` (~71 tokens)

Remove a crawled website

Remove one website crawl entry by its id, dropping the knowledge crawled from it. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `website_id` (string, required): Website entry id.

### `mba_list_files` (~73 tokens)

List knowledge files

List the files in the agent's knowledge base, as {id, file_name}. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_upload_file` (~281 tokens)

Upload a knowledge file

Upload a file into the agent's knowledge base. Multipart uploads cannot travel over MCP, so pass the file EITHER as `url` (a publicly reachable https URL this service downloads) OR as `content_base64` (the file's bytes, base64-encoded) - exactly one of the two, always with `file_name`. This service performs the multipart upload to Meta for you and returns the created {id, file_name}. Known limitations: Meta caps a file at 100 MB and accepts PDF, DOC, DOCX, PNG, JPG and JPEG (CSV and XLSX where enabled). Base64 content is additionally capped by this endpoint's request size limit, so prefer `url` for anything larger than a few megabytes. A `url` must be https and must resolve to a public address - private, loopback and link-local addresses are refused.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `content_base64` (string): The file's bytes, base64-encoded. Use `url` instead for large files.
- `file_name` (string, required): Name to store the file under, including its extension, e.g. 'returns-policy.pdf'.
- `url` (string): Publicly reachable https URL to download the file from.

### `mba_get_file` (~76 tokens)

Read knowledge file metadata

Read one knowledge file's metadata by its id. Returns {id, file_name} - this returns metadata only, not the file's contents.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `file_id` (string, required): Knowledge file id.

### `mba_delete_file` (~66 tokens)

Delete a knowledge file

Delete one file from the agent's knowledge base by its id. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `file_id` (string, required): Knowledge file id.

### `mba_list_agent_skills` (~89 tokens)

List agent skills

List the agent's skills - the instruction texts that shape how it behaves. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `agent_id` (string): Optional - restrict the list to one agent.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_create_agent_skill` (~154 tokens)

Create an agent skill

Add a skill to the agent - an instruction text that changes how it answers. Returns the created skill with its id. Skills are the right home for behavioural instructions; facts the agent should know belong in FAQs, websites or files instead.

Input parameters:

- `agent_id` (string): Optional - attach the skill to one agent.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `description` (string): What the skill is for (max 1024 characters).
- `skill` (string): The instruction text the agent follows (max 20000 characters).
- `title` (string): Short name for the skill (max 64 characters).

### `mba_get_agent_skill` (~70 tokens)

Read an agent skill

Read one agent skill by its id, as returned by mba_list_agent_skills or mba_create_agent_skill.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `skill_id` (string, required): Agent skill id.

### `mba_update_agent_skill` (~137 tokens)

Update an agent skill

Replace one agent skill by its id. This replaces the skill rather than patching it, so send the title, description and skill text you want it to end up with.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `description` (string): What the skill is for (max 1024 characters).
- `skill` (string): The instruction text the agent follows (max 20000 characters).
- `skill_id` (string, required): Agent skill id.
- `title` (string): Short name for the skill (max 64 characters).

### `mba_delete_agent_skill` (~69 tokens)

Delete an agent skill

Delete one agent skill by its id, so the agent stops following it. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `skill_id` (string, required): Agent skill id.

### `mba_list_ui_skills` (~237 tokens)

List UI skills

List the agent's UI skills - the rich WhatsApp components (carousels, CTA URLs, flows, images, interactive lists and buttons, location) the agent may send, each with the instruction that says when to send it. A UI skill is NOT an agent skill (mba_list_agent_skills): an agent skill is instruction text that shapes what the agent says, a UI skill lets the agent send one kind of rich WhatsApp component and tells it when to send that component. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

Input parameters:

- `after` (string): Cursor - return the page immediately after it.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `before` (string): Cursor - return the page immediately before it.
- `limit` (integer): Maximum entries per page. A page can be shorter.

### `mba_create_ui_skill` (~286 tokens)

Create a UI skill

Give the agent one more rich WhatsApp component to send, and the instruction that says when to send it. Returns the created UI skill with its id. A UI skill is NOT an agent skill (mba_list_agent_skills): an agent skill is instruction text that shapes what the agent says, a UI skill lets the agent send one kind of rich WhatsApp component and tells it when to send that component. Known limitation: component_type is FIXED AT CREATION and cannot be changed afterwards. flow_id is required when component_type is `flow`, and is refused for every other type; a flow UI skill also cannot be enabled until the flow itself is published.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `component_type` (string, required): The kind of rich message this UI skill sends. Cannot be changed after creation.
- `flow_id` (integer): The flow to send. Required when component_type is `flow`, refused otherwise.
- `instruction` (string, required): Tells the agent when to send this component, e.g. 'Send this when the customer asks to browse the catalog'.
- `status` (string, required): Whether the agent may send this component. Only an enabled UI skill is available to the agent.
- `title` (string, required): Human-readable name for the UI skill.

### `mba_get_ui_skill` (~121 tokens)

Read a UI skill

Read one UI skill by its id, as returned by mba_list_ui_skills or mba_create_ui_skill. A UI skill is NOT an agent skill (mba_list_agent_skills): an agent skill is instruction text that shapes what the agent says, a UI skill lets the agent send one kind of rich WhatsApp component and tells it when to send that component.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `instruction_id` (string, required): UI skill id.

### `mba_update_ui_skill` (~249 tokens)

Update a UI skill

Change the title, the status or the instruction of one UI skill by its id. This is a partial update: a field you omit keeps its stored value. Use it to enable or disable a component without deleting it. A UI skill is NOT an agent skill (mba_list_agent_skills): an agent skill is instruction text that shapes what the agent says, a UI skill lets the agent send one kind of rich WhatsApp component and tells it when to send that component. Known limitation: component_type and flow_id cannot be changed - delete the UI skill and create a new one instead. A flow UI skill cannot be enabled until its flow is published.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `instruction` (string): Tells the agent when to send this component, e.g. 'Send this when the customer asks to browse the catalog'.
- `instruction_id` (string, required): UI skill id.
- `status` (string): Whether the agent may send this component. Only an enabled UI skill is available to the agent.
- `title` (string): Human-readable name for the UI skill.

### `mba_delete_ui_skill` (~89 tokens)

Delete a UI skill

Delete one UI skill by its id, so the agent stops sending that component. Returns no content on success. To stop the component temporarily, set status to `disabled` with mba_update_ui_skill instead.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `instruction_id` (string, required): UI skill id.

### `mba_list_product_catalogs` (~207 tokens)

List product catalogs

List the Meta product catalogs connected to this channel's WhatsApp Business Account. Only id and name are returned unless `fields` asks for more. Use the catalog id with mba_list_catalog_products. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

Input parameters:

- `after` (string): Cursor - return the page immediately after it.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `before` (string): Cursor - return the page immediately before it.
- `fields` (string): Comma-separated fields to return, e.g. id,name,product_count,vertical. Default: id,name.
- `limit` (integer): Maximum entries per page. A page can be shorter.

### `mba_list_catalog_products` (~283 tokens)

List catalog products

List the products of one catalog connected to this channel's WhatsApp Business Account. A product's retailer_id is the product_retailer_id that product messages take. Known limitation: a catalog that is NOT CONNECTED to this WABA, or that does not exist, returns 403 Catalog not accessible - get valid ids from mba_list_product_catalogs. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

Input parameters:

- `after` (string): Cursor - return the page immediately after it.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `before` (string): Cursor - return the page immediately before it.
- `catalog_id` (string, required): The catalog ID, as list_product_catalogs returns it.
- `fields` (string): Comma-separated fields to return, e.g. id,retailer_id,name,price,image_url,availability.
- `filter` (string): Meta product filter as a JSON string, e.g. {"availability":{"eq":"in stock"}}.
- `limit` (integer): Maximum entries per page. A page can be shorter.

### `mba_get_commerce_settings` (~84 tokens)

Read commerce settings

Read this channel's WhatsApp commerce settings: whether the cart is enabled and whether the catalog is visible in the chat and on the business profile. Returns {data: [one entry]} with is_cart_enabled and is_catalog_visible.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_get_agent_budgets` (~279 tokens)

Read the agent budgets

Read the usage caps in force for the agent, each with its budget_id. Returns {budgets}; an empty array means no cap is set and usage is unlimited. Known limitations: budgets are ONLY SERVED for the business that owns this number's WABA; any other business_id is refused with an error that says so. For a number whose business is not known to 360dialog yet, budgets are not available and this tool returns an error that says so. When several caps are set, whichever is reached first stops the agent until its window resets, and the agent then hands conversations to the business. Token caps apply across the WHOLE BUSINESS MANAGER, so every agent in that portfolio shares them; AI-turn caps apply per conversation. These tools set and read caps and do not report usage against them: mba_get_agent_usage_insights reports billed usage, keyed on the billable account ID and not on business_id.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `business_id` (string, required): The Meta Business Manager ID of the business that owns this number's WABA. No other tool returns it: it is the WABA's owner business in Meta Business Suite, and the 360dialog hub shows it on the chan…

### `mba_replace_agent_budgets` (~363 tokens)

Replace the agent budgets

Set the usage caps for the agent. Returns the caps in force after the write. This is a FULL REPLACEMENT of the set: send again every cap to keep, because any cap left out is removed, and an empty array clears all caps and returns the agent to unlimited. To edit an existing cap, pass back its budget_id from mba_get_agent_budgets; omit budget_id to add a new cap. Two caps with the same unit_type and time_window pair are rejected. Known limitations: budgets are ONLY SERVED for the business that owns this number's WABA; any other business_id is refused with an error that says so. For a number whose business is not known to 360dialog yet, budgets are not available and this tool returns an error that says so. When several caps are set, whichever is reached first stops the agent until its window resets, and the agent then hands conversations to the business. Token caps apply across the WHOLE BUSINESS MANAGER, so every agent in that portfolio shares them; AI-turn caps apply per conversation. These tools set and read caps and do not report usage against them: mba_get_agent_usage_insights reports billed usage, keyed on the billable account ID and not on business_id.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `budgets` (array, required): The complete set of caps. An empty array removes every cap.
- `business_id` (string, required): The Meta Business Manager ID of the business that owns this number's WABA. No other tool returns it: it is the WABA's owner business in Meta Business Suite, and the 360dialog hub shows it on the chan…

### `mba_list_connectors` (~97 tokens)

List connectors

List the agent's connectors - the third-party systems it can call. Each carries a connection_status (PENDING_OAUTH, ACTIVE, EXPIRED or ERROR) worth checking before relying on its tools. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_create_connector` (~241 tokens)

Create a connector

Create a connector so the agent can call a third-party system. Returns the connector with its id and connection_status. A connector on its own does nothing - add connector tools with mba_create_connector_tool to expose individual operations to the agent.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `auth_config` (object): Credentials matching auth_type: `api_key` when auth_type is API_KEY, `oauth2_client_credentials` when it is OAUTH2_CLIENT_CREDENTIALS. Credentials can also be set later with upsert_connector_api_key…
- `auth_type` (string, required): How the connected system authenticates.
- `base_url` (string, required): Base URL every tool on this connector calls.
- `description` (string, required): What the connected system does.
- `name` (string, required): Name of the connector.
- `requires_certificate` (boolean): True when the system needs mTLS; upload the certificate with upsert_connector_certificate.
- `user_auth_injection_config` (object): Optional configuration for injecting a per-user token into tool requests.

### `mba_get_connector` (~76 tokens)

Read a connector

Read one connector by its id, including its connection_status and mTLS metadata. Credentials are never returned - the private key and secrets stay at Meta.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.

### `mba_update_connector` (~240 tokens)

Update a connector

Replace one connector by its id. This replaces the connector rather than patching it, so send the full definition you want it to end up with - read mba_get_connector first.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `auth_config` (object): Credentials matching auth_type: `api_key` when auth_type is API_KEY, `oauth2_client_credentials` when it is OAUTH2_CLIENT_CREDENTIALS. Credentials can also be set later with upsert_connector_api_key…
- `auth_type` (string, required): How the connected system authenticates.
- `base_url` (string, required): Base URL every tool on this connector calls.
- `connector_id` (string, required): Connector id.
- `description` (string, required): What the connected system does.
- `name` (string, required): Name of the connector.
- `requires_certificate` (boolean): True when the system needs mTLS; upload the certificate with upsert_connector_certificate.
- `user_auth_injection_config` (object): Optional configuration for injecting a per-user token into tool requests.

### `mba_delete_connector` (~68 tokens)

Delete a connector

Delete one connector by its id. Its tools and stored credentials go with it. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.

### `mba_upsert_connector_api_key` (~123 tokens)

Set connector API key

Set or rotate the API key credentials for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required.

Input parameters:

- `api_key_config` (object, required): Where the API key is injected. Supply at least one of headers, query_params, body_params.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.

### `mba_upsert_connector_oauth` (~114 tokens)

Set connector OAuth credentials

Set or rotate the OAuth 2.0 client credentials for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `oauth_config` (object, required): OAuth 2.0 client credentials.

### `mba_upsert_connector_certificate` (~162 tokens)

Set connector mTLS certificate

Upload or rotate the mTLS client certificate for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required. Certificates and keys are PEM-encoded; the private key is never returned by any read tool.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `ca_certificate` (string): Optional PEM-encoded CA certificate.
- `client_certificate` (string, required): PEM-encoded client certificate.
- `client_key` (string, required): PEM-encoded private key (PKCS8, RSA or EC).
- `connector_id` (string, required): Connector id.

### `mba_get_connector_logs` (~255 tokens)

Read connector logs

Read the connector's third-party error logs, or aggregated failure patterns when summary_only is true. Only errors from the third-party system are included, so an empty result means no failures, not no traffic. Known limitation: the time range must not exceed 7 DAYS, and only the last 7 days are retained - start_time defaults to 24 hours ago and end_time to now. Unlike the other list tools this one does return an object: {data: [...], stats: {...}}, with stats present only when include_stats is true.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `end_time` (integer): End of the range, Unix seconds.
- `include_stats` (boolean): Add aggregate statistics.
- `limit` (integer): Default 100.
- `start_time` (integer): Start of the range, Unix seconds. Must be within the last 7 days.
- `summary_only` (boolean): Return failure patterns instead of entries.
- `tool_id` (string): Restrict to one connector tool.
- `top_n` (integer): Default 10.

### `mba_list_connector_tools` (~75 tokens)

List connector tools

List the actions defined on one connector. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.

### `mba_create_connector_tool` (~254 tokens)

Create a connector tool

Define one action the agent can perform through a connector - an outbound HTTP request against the connector's base_url. Returns the created tool with its id. Known limitation: path_parameters, query_parameters and headers are NAME-TO-SCHEMA OBJECTS, not arrays - write {"order_id": {"type": "string"}}, never [{"name": "order_id", ...}]. And every {brace} token in `path` must have a matching key in path_parameters, or the definition is rejected.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `description` (string, required): What the action does - the agent uses this to decide when to call it.
- `name` (string, required): Name the agent sees for this action.
- `request_definition` (object, required): The outbound HTTP request this tool makes, relative to the connector's base_url.
- `user_auth_action_config` (object): Optional login/refresh response extraction config, for user-auth actions.
- `user_auth_required` (boolean, required): True when the call needs a per-user token rather than the connector's own credentials.

### `mba_get_connector_tool` (~67 tokens)

Read a connector tool

Read one connector tool definition by its id.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `tool_id` (string, required): Connector tool id.

### `mba_update_connector_tool` (~275 tokens)

Update a connector tool

Replace one connector tool definition by its id. This replaces the definition rather than patching it, so send the whole request_definition you want it to end up with - read mba_get_connector_tool first. Known limitation: path_parameters, query_parameters and headers are NAME-TO-SCHEMA OBJECTS, not arrays - write {"order_id": {"type": "string"}}, never [{"name": "order_id", ...}]. And every {brace} token in `path` must have a matching key in path_parameters, or the definition is rejected.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `description` (string, required): What the action does - the agent uses this to decide when to call it.
- `name` (string, required): Name the agent sees for this action.
- `request_definition` (object, required): The outbound HTTP request this tool makes, relative to the connector's base_url.
- `tool_id` (string, required): Connector tool id.
- `user_auth_action_config` (object): Optional login/refresh response extraction config, for user-auth actions.
- `user_auth_required` (boolean, required): True when the call needs a per-user token rather than the connector's own credentials.

### `mba_delete_connector_tool` (~83 tokens)

Delete a connector tool

Delete one connector tool definition by its id, so the agent can no longer perform that action. Returns no content on success.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `tool_id` (string, required): Connector tool id.

### `mba_run_connector_tool` (~213 tokens)

Run a connector tool

Execute one connector tool once, as the agent would, and return what the third-party system answered. Use it to check a definition works before relying on it. `input` is a JSON-ENCODED STRING of the arguments, not an object. Known limitation: the result is DOUBLY STRINGIFIED - the response is {output, status} where `output` is a JSON string; parse `output`, then parse its `.body` to reach the third-party system's actual response. What this call does depends entirely on the tool being run: it can create, change or delete data in the connected system.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `connector_id` (string, required): Connector id.
- `input` (string): Arguments as a JSON-encoded string, e.g. '{"order_id":"123"}'. Defaults to an empty object.
- `tool_id` (string, required): Connector tool id.

### `mba_send_agent_event` (~163 tokens)

Send an agent event

Trigger the agent to act on a consumer conversation asynchronously - the event is queued and the call returns immediately with status "accepted" and an agent_event_id. Poll mba_get_agent_event with that id to find out what happened; a 202-style acknowledgement here does not mean the consumer was messaged. Known limitation: event.payload must be a JSON-ESCAPED STRING, not an object - pass "{\"order_id\":\"123\"}", not {"order_id": "123"}. Maximum 4096 characters.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `event` (object, required)
- `to` (string, required): Consumer's WhatsApp number in E.164 format.

### `mba_get_agent_event` (~111 tokens)

Read agent event status

Read the processing status of an event submitted with mba_send_agent_event. Status is one of request_received, processing, sent, failed, skipped or success; failed and skipped carry error_message and skipped_reason. This is the only way to find out whether an accepted event actually reached the consumer.

Input parameters:

- `agent_event_id` (string, required): Event id returned by send_agent_event.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_test_agent` (~152 tokens)

Test the agent

Send a test message through the full agent pipeline and read its reply, without needing a real consumer number. Pass conversation_id from a previous reply to continue the same test conversation. Known limitation: while ai_audience is ALLOWLISTED_ONLY this returns agent_response: "" with no_response_reason: "ELIGIBILITY_CHECK_FAILED", no matter which consumer number is involved - check mba_get_agent_settings before concluding the agent is broken.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `conversation_id` (string): Optional - continue an existing test conversation.
- `user_msg` (string, required): The message to send to the agent.

### `mba_release_thread_control` (~93 tokens)

Release thread control

Hand a consumer conversation back to the Meta Business Agent as the automatic responder, after a human agent has taken it over. Only releasing is supported here - taking control is restricted to configured escalation partners.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `to` (string, required): Consumer's WhatsApp number in E.164 format.

### `mba_send_message` (~200 tokens)

Send a WhatsApp message

Send a WhatsApp message to a consumer and release thread control back to the agent. The body is the WhatsApp Cloud API message object - set `type` and the matching payload key (text, template, interactive, image, ...). This messages a real person: it is subject to the platform's send eligibility rules, and outside a 24-hour customer service window only an approved template will be delivered.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `recipient_type` (string): Defaults to individual.
- `template` (object): Used when type is template.
- `text` (object): Used when type is text, e.g. {"body": "Hello"}.
- `to` (string, required): Consumer's WhatsApp number in E.164 format.
- `type` (string, required): Message type, e.g. text, template, interactive, image.

### `mba_list_eval_cases` (~71 tokens)

List evaluation cases

List the evaluation scenarios configured for this agent, each with its scenario text, categories, max_turns and success criteria. Their ids are what mba_start_eval_run takes.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

### `mba_start_eval_run` (~153 tokens)

Start an evaluation run

Submit an evaluation job that simulates the listed cases against the agent, evaluates the conversations and optionally produces insights. Returns {job_id, status: QUEUED} - the work is asynchronous, so poll mba_get_eval_results with the job_id. Known limitation: eval_case_ids is read from the QUERY STRING, not the request body - pass it as the comma-separated argument here and this service puts it in the right place; the body is a separate object that accepts nothing else.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `eval_case_ids` (string, required): Comma-separated eval case ids from list_eval_cases.

### `mba_get_eval_results` (~179 tokens)

Read evaluation results

Read an evaluation job by its job_id. While the job runs this gives the status (QUEUED or RUNNING) and the progress. When the job fails it gives the error. When the job completes it gives the aggregated report: the summary text, the average conversation and turn scores, the highlights and the top failure categories. There is no separate summary call: a completed job already carries that report. For the per-conversation transcripts and per-turn labels, take the ids from `eval_ids_by_score` and call mba_get_eval_details. This tool adds a `details` key when it can read those ids for you.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `job_id` (string, required): Job id returned by start_eval_run.

### `mba_get_eval_details` (~128 tokens)

Read evaluation details

Read per-conversation evaluation results - scores, per-turn labels, reasons and the transcript. Takes eval_ids, which is a different kind of id from the job_id that mba_get_eval_results takes. Read them from the eval_ids_by_score field of a completed job. mba_get_eval_results already adds these details when it can read that field, so call this tool when it could not.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `eval_ids` (string, required): Comma-separated evaluation ids.

### `mba_get_agent_event_insights` (~223 tokens)

Read agent event insights

Read what happened to the events sent to the agent (mba_send_agent_event) over a date range, one row per event type, busiest first: how many were received, how many the agent successfully processed, and the mean end-to-end latency. Successfully processed means the agent sent its message, not that the message was delivered. Figures are rolled up once a day, so the most recent day may still be incomplete. Known limitation: the dates are in PACIFIC TIME, not the business time zone, and the range may span at most 30 days, counting both ends.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `end_date` (string, required): Last day to include, YYYY-MM-DD in Pacific Time. Inclusive.
- `event_type` (string): Return only this event type, named as it was sent. Omit for every event type.
- `start_date` (string, required): First day to include, YYYY-MM-DD in Pacific Time. Inclusive.

### `mba_get_conversation_turns` (~362 tokens)

Read conversation turns

Read the ordered turns of the most recent conversation between the agent and one customer. Each turn carries its turn_id, conversation_id and the observed steps - LLM calls with a preview of the model output, and tool calls with the tool name, input and output - plus latency and status where available. Use it to see why the agent answered the way it did. Malformed records, and tool responses that cannot be matched to a tool call, may be missing. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

Input parameters:

- `after` (string): Cursor - return the page immediately after it.
- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `before` (string): Cursor - return the page immediately before it.
- `end_timestamp_ms` (integer): Only turns that started at or before this Unix time in milliseconds.
- `limit` (integer): Maximum entries per page. A page can be shorter.
- `start_timestamp_ms` (integer): Only turns that started at or after this Unix time in milliseconds.
- `user_phone_number` (string, required): The customer: a phone number in digits only with the country code (15551234567, no + or separators), a Business-Scoped User ID such as US.2788620304833812, or the conversation_id returned by test_age…

### `mba_get_conversation_insights` (~235 tokens)

Read conversation insights

Read how many conversations the agent replied in over a date range (ai_threads), and how many are currently handed from the agent to the business and still awaiting a business reply (ai_handoffs). Counts are per conversation, not per message, and match the business's own agent summaries. Returns {data: [one row]}, each metric as {count}, present only when requested. Known limitation: ai_handoffs is a SNAPSHOT of the present moment - it ignores start_date and end_date. The range may span at most 90 days, counting both ends, and each requested metric costs a separate scan, so ask only for what you need.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `end_date` (string, required): Last day to include, YYYY-MM-DD in the business time zone. Inclusive.
- `metrics` (array): Which metrics to return. Omit for all of them.
- `start_date` (string, required): First day to include, YYYY-MM-DD in the business time zone. Inclusive.

### `mba_get_tool_call_insights` (~229 tokens)

Read tool call insights

Read how each of the business's own tools performed over a date range, one row per tool, busiest first: how many conversations called it, its mean latency, and its success, error and timeout rates (0 to 1; timeouts count as errors too). Only tools the business supplied are reported. thread_count counts a conversation once per day, so one that called the tool on three days counts three times. Figures are rolled up once a day, so the most recent day may still be incomplete. Known limitation: the range may span at most 30 days, counting both ends.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `end_date` (string, required): Last day to include, YYYY-MM-DD in the business time zone. Inclusive.
- `start_date` (string, required): First day to include, YYYY-MM-DD in the business time zone. Inclusive.
- `tool_name` (string): Return only this tool, named as it was registered. Omit for every tool called.

### `mba_get_agent_usage_insights` (~437 tokens)

Read agent usage insights

Read the billed usage of a Meta Business Agent account over a billing date range, one entry per HOUR, DAY or MONTH bucket: billable messages, billable tokens, and cost in the account's currency. Returns {usage}; an empty array means no usage in the range. Each entry carries its bucket start and end (Unix seconds, end exclusive), plus channel and sender_id when they are in dimensions. Metrics left out of metric_types are omitted from every entry, not returned as null. Tokens are BILLED tokens, the figure on the invoice, which can be fewer than the tokens the agent consumed. Known limitations: usage insights are ONLY AVAILABLE for numbers whose stack uses its own WABA access token; for any other number this tool returns an error that says so. The range is start INCLUSIVE, end EXCLUSIVE, and dates are evaluated in the billable account's timezone, so a day bucket can be 23 or 25 hours long. MONTH needs a range of whole months: start on the 1st, end on the last day of a month.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
- `billable_account_id` (string, required): The billable account ID of the Meta Business Agent account. No other tool returns it: Meta Billing Hub shows it under Accounts > Meta Business Agent accounts. It is not the Business Manager ID the bu…
- `channels` (array): Only usage on these messaging surfaces.
- `dimensions` (array): Split each bucket by these axes. Omit to total the whole agent per bucket.
- `end` (integer, required): End of the range, Unix seconds. Exclusive: buckets that start before it.
- `granularity` (string, required): Size of each bucket.
- `metric_types` (array): Which metrics to return. Omit for all of them.
- `sender_ids` (array): Only usage attributed to these sending entities.
- `start` (integer, required): Start of the range, Unix seconds. Inclusive: buckets that start at or after it.

### `mba_get_agent_state` (~128 tokens)

Read agent state

Read whether this channel has ever been onboarded and whether its agent has ever been activated, as {onboarded, activated_once}. Known limitation: this is NOT a Meta call - it reads this service's own tracking record, written when onboarding or a settings read/write goes through here. It answers 'did onboarding ever succeed' and 'was rollout ever enabled', and nothing about the agent's current configuration. For live state call mba_get_agent_settings.

Input parameters:

- `app_id` (string, required): The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-360dialog-mcp/mcp#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 77
- 2026-11-12: 76
- 2026-11-11: 76
- 2026-11-10: 75
- 2026-11-09: 75
- 2026-11-08: 74

## Common questions

### What is the 360dialog MCP server?

360dialog is an MCP server listed in the public MCP registry as com.360dialog/mcp. Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more. This page covers its hosted endpoint (https://mcp.360dialog.com/mcp).

### Is the 360dialog MCP server safe to use?

360dialog scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 360dialog MCP server expose?

360dialog exposes 138 tools: list_skills, get_skill, start_signup, search_client_documentation, get_client_documentation_page, and 133 more. Their descriptions and schemas cost roughly 20,275 tokens of context every time the server is loaded.

### Does the 360dialog MCP server require authentication?

Yes. 360dialog asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the 360dialog MCP server still maintained?

360dialog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the 360dialog MCP server?

VerifyMCP ran 14 checks on 360dialog, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.360dialog.com/mcp
- Website: https://www.360dialog.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-360dialog-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-360dialog-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-360dialog-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-360dialog-mcp/mcp
