Skip to main content
Glama

Fix a WhatsApp template

dosai_edit_whatsapp_template
Destructive

Replace the text of a template that is approved, rejected or paused: it goes back to Meta review (an approved one can be edited once a day). Same body rules as create. 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>",
      "body": "<body>",
      "variables": "<variables>"
    },
    "name": "dosai_edit_whatsapp_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
titleNo
categoryNo
variablesYes
project_idYesFrom dosai_list_projects.
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the edit resets the template to Meta review, there is a once-per-day cap on approved templates, and an admin/owner permission requirement. The destructiveHint is implicitly explained by the review reset, though it never states what happens to in-flight sends or whether the prior text is recoverable.

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?

A single dense sentence that front-loads the action and eligibility, with rate limit and permissions appended. Nothing is wasted, but the parenthetical and the create cross-reference make it slightly harder to parse than it needs to be.

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?

With six parameters, no output schema, and low schema coverage, the description covers state transitions and permissions well but leaves parameter-level meaning largely unaddressed. Adequate to select the tool, insufficient to invoke it confidently without consulting the schema or a sibling.

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 description coverage is only 17%, and the description compensates only with the vague pointer "Same body rules as create" rather than spelling out body length, variable count, title, or category constraints. An agent must open the create tool's definition to learn the actual rules for four required parameters.

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 ("Replace the text of a template") plus the eligible states, which cleanly separates it from create_whatsapp_template and delete_whatsapp_template without needing the schema.

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

Usage Guidelines4/5

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

Gives concrete preconditions for use: the template must be approved, rejected, or paused, approved ones are editable only once per day, and the caller must be admin or owner. It does not explicitly route to a sibling (e.g. create vs edit), but the eligibility rules make the when-to-use boundary clear.

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