Skip to main content
Glama

Create a WhatsApp template

dosai_create_whatsapp_template

Send a template to Meta for review (usually hours, the owner is notified). purpose=all_ready_made: every ready-made template the number lacks in this language. A ready-made purpose without body: that one as is. purpose=custom: own text with title, category, body and variables; body uses {{1}}…{{n}} in order, never as the first or last word, variables names them in the same order (custom may use only "name"). Creating is free, each send costs the owner money at Meta. 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>",
      "purpose": "<purpose>",
      "language": "<language>"
    },
    "name": "dosai_create_whatsapp_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
titleNo
purposeYes
categoryNo
languageYes
variablesNo
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful behavior: Meta review usually takes hours, the owner is notified, creation is free, sends cost money, and the caller must be an admin or owner. It does not describe the return value or failure states, but it adds substantial operational context for a write operation.

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

Conciseness3/5

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

The core action is front-loaded and the text is compact, but several phrases are telegraphic or cryptic, especially 'A ready-made purpose without body: that one as is' and 'variables names them in the same order.' The information density is high, but parsing suffers from sentence fragments.

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 seven-parameter write tool with no output schema, the description covers the main workflow, purpose modes, variable syntax, cost, and authorization. It still omits return/status information, category and language semantics, and clear required-field expectations for each purpose mode.

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 description coverage is only 14%, and the description compensates well by explaining purpose modes and the custom body/variable syntax, including ordered {{1}}…{{n}} placeholders, the first/last-word rule, and the 'name' variable restriction. It still leaves category and language enum meanings unexplained.

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 states a specific action and resource: 'Send a template to Meta for review.' This clearly identifies a create/submit operation rather than listing, editing, deleting, or sending a live message, although it does not explicitly name the sibling tools or contrast with them.

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?

It provides useful guidance for the purpose modes, including all_ready_made and custom, but does not explicitly say when to use this tool versus dosai_edit_whatsapp_template, dosai_send_whatsapp_template, or dosai_list_whatsapp_templates. The creation context is implied rather than stated as an exclusion rule.

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