Skip to main content
Glama

update_whatsapp_number_settings

Idempotent

Change the AI behaviour of ONE WhatsApp number assigned to a Convocore agent (get phoneId from get_whatsapp_ai_rules). Partial update: send only the fields to change. Use aiPaused to stop/resume all AI replies on the number, and coexistenceSettings for numbers shared with the WhatsApp Business app. Does not connect, reassign or remove numbers, and never touches Meta credentials. For reply conditions (phrases, AI rule, schedule, allow/deny list) use update_whatsapp_ai_rules.

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": {
      "agentId": "<agentId>",
      "phoneId": "<phoneId>",
      "settings": "<settings>"
    },
    "name": "update_whatsapp_number_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesAgent the number is assigned to.
phoneIdYesMeta WhatsApp phone number ID (not the phone number itself).
settingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare idempotent, non-destructive, closed-world. The description adds real behavioral context beyond them: partial-merge semantics, nested sub-fields merged individually, legacy fields that only apply while AI rules are disabled, and explicit non-actions (no credentials/reassignment). This is the kind of scope disclosure an agent needs before mutating settings.

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?

Front-loaded with the core action and scope, then routing to the dependency, then the partial-update note, then exclusions and the sibling pointer. Dense but every sentence carries routing or behavioral information.

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

Completeness5/5

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

For a nested-object mutation tool with no output schema, the description covers scope, partial-update behavior, key field semantics, prerequisites (phoneId source), and boundaries against adjacent tools. Nothing an agent needs to invoke it safely is missing beyond the one undocumented boolean.

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

Parameters4/5

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

Schema coverage is 67%, so the schema carries most of the load, but the description adds meaning for aiPaused and coexistenceSettings usage. It doesn't explain applyAiReplyRuleDuringHumanChatting, which is undocumented in both the description and the schema, leaving a small gap.

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

Purpose5/5

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

States a specific verb and resource — 'Change the AI behaviour of ONE WhatsApp number assigned to a Convocore agent' — with explicit scope (one number). It clearly demarcates itself from update_whatsapp_ai_rules and the whatsapp_numbers_* siblings.

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

Usage Guidelines5/5

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

Explicitly says how to obtain phoneId (get_whatsapp_ai_rules), that it's a partial update (send only changed fields), when to use aiPaused and coexistenceSettings, and what it does NOT do (connect, reassign, remove, touch Meta credentials). It also names the sibling for reply conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources