Skip to main content
Glama

Delete a WhatsApp template

dosai_delete_whatsapp_template
Destructive

Delete one template (this language version) at Meta and in the project. Two steps. 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>",
      "template_id": "<template_id>"
    },
    "name": "dosai_delete_whatsapp_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
template_idYes
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context the annotations do not: deletion propagates to Meta's remote state as well as the local project, it affects only one language version, and it requires admin/owner rights. The vague "Two steps" is fleshed out only by the confirm_token schema description rather than the prose itself.

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?

The destructive verb and scope are front-loaded in the first clause, and nothing is padded. The fragmentary "Two steps." is terse to the edge of cryptic, costing it a point on clarity.

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?

For a destructive, two-required-parameter tool with no output schema, the description covers what is deleted, where, and who may do it, and the confirm_token schema carries the safety flow. It stops short of stating irreversibility or what happens to an approved/in-use template.

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?

With 67% schema description coverage, the schema does most of the work: project_id's provenance and the elaborate confirm_token protocol are documented there. The description adds only an indirect hint ("Two steps", "Admin or owner") and contributes nothing about template_id, so it does not meaningfully exceed the schema baseline.

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?

The description names a specific verb and resource ("Delete one template") and adds a scoping qualifier, "(this language version)", plus the dual location "at Meta and in the project". That scoping is genuinely discriminating for an agent, though no sibling tool is named as an alternative.

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?

"Admin or owner" supplies a real prerequisite and "Two steps" signals a non-trivial call flow, which is useful. However, there is no explicit statement of when to choose this over editing or archiving a template, and no when-not guidance, leaving usage largely implied.

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