whatsapp_delete_chat
Delete a WhatsApp chat by providing its chat JID. Removes the specified conversation from your WhatsApp account.
Instructions
Delete a chat.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chatId | Yes | Chat JID |
Delete a WhatsApp chat by providing its chat JID. Removes the specified conversation from your WhatsApp account.
Delete a chat.
| Name | Required | Description | Default |
|---|---|---|---|
| chatId | Yes | Chat JID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No behavioral traits are disclosed. The description does not clarify whether deletion is permanent, reversible, or requires special permissions. With no annotations provided, the description carries the full burden but fails to convey critical behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
At two words, the description is under-specified. While brevity is valued, it sacrifices informational value. A single sentence could have added needed context without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is incomplete for a deletion tool. It does not mention irreversibility, impact on messages, or any confirmation steps. Given the simplicity of the tool (one parameter, no output schema), more context is needed for safe usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear parameter description ('Chat JID'). The 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a chat' clearly states the action and resource. It is a specific verb+resource pair, distinguishing it from siblings like 'clear_chat' which clears messages without deleting the chat. However, it does not elaborate on scope or effects.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., when to delete vs archive or clear), and no prerequisites or caveats are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wsapi-chat/wsapi-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server