Evolution API WhatsApp MCP Server

get_template

Retrieve a specific WhatsApp Business message template by ID for use in automated messaging workflows and customer communications.

Instructions

Get a specific template by ID

Input Schema

TableJSON Schema

Name	Required	Description	Default
`templateId`	Yes	Template ID

Implementation Reference

src/index.ts:730-743 (handler)

Main handler function for the 'get_template' tool. Retrieves the template by ID using templateService and returns it as JSON text content.

private async handleGetTemplate(args: any) {
  const template = templateService.getTemplate(args.templateId);
  if (!template) {
    throw new Error(`Template ${args.templateId} not found`);
  }
  return {
    content: [
      {
        type: 'text',
        text: JSON.stringify(template, null, 2)
      }
    ]
  };
}

src/index.ts:213-222 (schema)

Tool registration in the tools list including input schema definition requiring 'templateId'.

  name: 'get_template',
  description: 'Get a specific template by ID',
  inputSchema: {
    type: 'object',
    properties: {
      templateId: { type: 'string', description: 'Template ID' }
    },
    required: ['templateId']
  }
},

src/index.ts:510-511 (registration)
Dispatch case in the main CallToolRequestHandler switch statement that routes to the specific handler.
```
case 'get_template':
  return await this.handleGetTemplate(args);
```
src/services/template-service.ts:110-112 (helper)
Core helper method in templateService that fetches a template from the internal Map by ID.
```
getTemplate(id: string): MessageTemplate | undefined {
  return this.templates.get(id);
}
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2025

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'Get', omitting behavior on missing template, return format, or errors.

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?

Single concise sentence, front-loaded with key information, no filler words.

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?

Minimally adequate for a simple get operation, but lacks details about return value, error handling, or prerequisites given no output schema.

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 coverage is 100% and schema already describes templateId; the description adds no extra meaning, just restates 'by ID'.

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?

Clearly states verb 'Get' and resource 'specific template by ID', distinguishing it from siblings like list_templates, create_template, etc.

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?

No explicit guidance on when to use this tool vs alternatives; implied usage from the description but no exclusions or context.

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