Convertway WhatsApp MCP Server

list_templates_by_module

Retrieve all message templates associated with a given module, such as shipment or payment, to manage and organize your communications.

Instructions

List all templates for a specific module

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": {
      "module": "<module>"
    },
    "name": "list_templates_by_module"
  }
}

Input Schema

Name	Required	Description	Default
`module`	Yes	Module name (e.g. shipment, payment, support, alerts, b2b, escalation)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states 'List all templates', which is a read operation, but does not mention any behavioral traits such as pagination, ordering, rate limits, or result format. The minimal description leaves significant gaps.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. Every word contributes meaning, and it is appropriately concise for the simple tool.

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?

Given the tool's simplicity (one parameter, no output schema), the description is nearly complete. It states the purpose and the filtering aspect. Minor improvement could be a note about return type, but it is sufficient for a basic list endpoint.

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 description coverage is 100% for the sole parameter 'module', which already includes a list of example values. The tool description ('for a specific module') adds no extra meaning beyond the schema. Baseline of 3 is appropriate given complete schema coverage.

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 'List', the resource 'templates', and the scope 'for a specific module'. This distinguishes it from sibling tools like 'list_all_templates' (no module filter) and 'list_template_modules' (lists modules themselves).

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?

The description implies that the tool is for retrieving templates for a given module, but it does not explicitly state when to use this tool over alternatives like 'list_all_templates' or 'list_template_modules'. The usage context is implied by the name and scope.

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

Deploy Server