Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

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
NameRequiredDescriptionDefault
templateIdYesTemplate ID

Implementation Reference

  • 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)
          }
        ]
      };
    }
  • 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);
  • 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);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits like read-only status, error handling, authentication needs, or rate limits. It lacks details on what 'Get' entails beyond the minimal operation.

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, efficient sentence with no wasted words, making it easy to parse and front-loaded with the core purpose. It earns its place by directly stating the tool's function.

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 lack of annotations and output schema, the description is incomplete for a retrieval tool. It doesn't explain return values, error cases, or behavioral context, leaving significant gaps for an agent to understand full usage.

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%, so the schema fully documents the 'templateId' parameter. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 clearly states the action ('Get') and resource ('a specific template by ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_templates' or 'search_templates', which would require explicit scope clarification for a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'list_templates' or 'search_templates'. The description implies usage for retrieving a single template by ID but offers no context about prerequisites, exclusions, or comparisons to siblings.

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/luiso2/mcp-evolution-api'

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