Skip to main content
Glama

Change the WhatsApp business profile

dosai_update_whatsapp_profile
Destructive

Change the public profile of the official WhatsApp number: only the fields you pass, clients see it at once. about cannot be emptied; the photo is uploaded in the cabinet. Admin or owner.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_update_whatsapp_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
aboutNo
emailNo
addressNo
verticalNo
websitesNo
project_idYesFrom dosai_list_projects.
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=true), the description usefully discloses that changes are immediately client-visible and that 'about cannot be emptied' – real behavioral constraints. It still omits rollback/reversibility, whether existing values are overwritten, and what the photo/'cabinet' statement actually means, leaving the mutation profile partly unexplained.

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

Conciseness4/5

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

Two compact sentences with the scope and partial-update rule front-loaded. The 'photo is uploaded in the cabinet' fragment is wasted/mystifying space, but overall it's efficiently sized.

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

Completeness3/5

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

For a 7-parameter mutation with 14% schema coverage and no output schema, the description covers permissions, partial-update behavior, and one field constraint but leaves the majority of parameters undocumented. An agent could invoke it but would be guessing on most field semantics.

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

Parameters2/5

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

Schema coverage is only 14% of 7 params – only project_id is documented in the schema. The description names just 'about' (with a non-obvious non-empty constraint) and alludes vaguely to a photo field that isn't even in the schema, leaving email, address, vertical enum, websites limit, and description entirely unexplained. It does not compensate for the low coverage.

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+resource: 'Change the public profile of the official WhatsApp number.' That clearly separates it from the get_whatsapp_profile sibling. It stops short of explicitly naming the read counterpart or other update_* tools, so it doesn't fully earn a 5.

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?

'only the fields you pass' conveys partial-update semantics and 'Admin or owner' states the permission gate, which is genuine usage context. However, there is no explicit when-to-use vs. when-not guidance, and the cryptic 'the photo is uploaded in the cabinet' clause gives no actionable instruction.

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