Skip to main content
Glama
Eyalm321
by Eyalm321

zernio_delete_whatsapp_template

Delete a WhatsApp Business message template by providing the template name and account ID. Remove unwanted templates from your WhatsApp Business account.

Instructions

Delete a WhatsApp Business message template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNameYesThe template name to delete
accountIdYesThe WhatsApp Business account ID
Behavior2/5

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It only states 'delete', which implies destruction, but fails to specify whether deletion is permanent, reversible, or what happens to active messages using the template. Critical safety information is missing.

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 description is a single sentence, which is concise but lacks necessary detail. While not verbose, it sacrifices completeness for brevity. It earns a middling score because it is not overly long but also not sufficiently informative.

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

Completeness2/5

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

Given the presence of sibling tools for WhatsApp templates and other delete operations, the description only states the basic action. It provides no information about return values, success/error behavior, or side effects. For a delete tool, this is insufficient for an AI agent to fully understand the operation's implications.

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?

Schema coverage is 100% with both parameters (templateName, accountId) having clear descriptions in the schema. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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?

The description clearly states the verb 'delete' and the resource 'WhatsApp Business message template', making the tool's purpose immediately obvious. It effectively distinguishes this tool from related siblings like create, update, get, and list WhatsApp template tools, as well as other delete tools.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., template existence, permissions), and no mention of preconditions or postconditions. The agent is left without context for proper invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/zernio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server