360dialog

Update channel profile

update_channel_profile

Destructive

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "new_profile": "<new_profile>",
      "channel_id": "<channel_id>",
      "project_id": "<project_id>"
    },
    "name": "update_channel_profile"
  }
}

Input Schema

Name	Required	Description
`channel_id`	Yes	Needs to end with 'CH'.
`project_id`	Yes	Needs to end with 'PR'.
`new_profile`	Yes	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 the JSON. e.g. JSON with no changes: {} e.g. JSON that only changes about text: { "about_text": "Hello world" }

Output Schema

Name	Required	Description	Default
`message`	Yes
`updated`	Yes
`channel_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description's job is to add context, and it does: it discloses that a third-party provider (360Dialog) may interrupt the flow with an email OTP, which the agent must communicate. It does not explain what makes the operation destructive or how partial clears propagate, leaving that to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded statements: purpose first, then the user-facing caveat. No filler, no repetition of schema or annotation content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and rich param descriptions are supplied, so the description needn't cover return values, and it covers the one non-obvious runtime behavior (OTP). What is missing for a destructive, third-party-mediated mutation is a note on whether changes take effect immediately or are subject to WhatsApp review.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the nested PATCH semantics and an example for new_profile, so parameter meaning is already fully carried by the schema. The description adds only one semantic detail beyond it, the channel_id-is-a-phone-number equivalence; the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Update the WhatsApp profile for this channel," and clarifies that a channel is a phone number, which helps separate it from generic company-level updates. It implicitly contrasts with the read sibling get_channel_profile via the update verb, but never names it or set_display_name as adjacent alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides genuine operational guidance for the OTP step (360Dialog may email a code; warn the user), which tells the agent how to run the call. It gives no guidance on when to choose this tool over get_channel_profile or set_display_name, and no prerequisites such as needing an existing profile or verified number.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 360dialog tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?