Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get WhatsApp Template

get-whatsapp-template
Read-onlyIdempotent

Retrieve a WhatsApp template by ID to view its content, required parameters, approval status, category, and rejection reason, so you can confirm what a send must fill before drafting.

Instructions

Get one WhatsApp template: its content, the parameters a send must fill, its approval status and, when Meta rejected it, the rejection_reason. pending is under review by Meta, and paused and disabled are applied by Meta for low quality. category can differ from what was submitted, because Meta recategorizes templates and the category sets the price per message.

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": {
      "id": "<id>"
    },
    "name": "get-whatsapp-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe WhatsApp template id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description still adds genuine domain value by decoding status values (pending under review; paused/disabled applied by Meta for low quality) and warning that category can be recategorized by Meta and drives per-message pricing. It does not cover error/not-found behavior.

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?

Three tight sentences, front-loaded with what is returned, followed by two scoping facts that change interpretation of the response. No filler or repetition.

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?

With no output schema, the description must carry return-value meaning, and it does so for the key fields (content, parameters, status, rejection_reason, category). Missing only the not-found/error case and any note on which fields are always present, which keeps it just short of complete.

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 a single uuid-formatted id parameter that the schema fully documents. The description adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource, 'Get one WhatsApp template,' and immediately enumerates the returned fields (content, parameters, status, rejection_reason). The word 'one' implicitly contrasts with the sibling list-whatsapp-templates, though no alternative is named explicitly.

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?

Usage is only implied: an agent can infer this fetches a single template by id rather than listing or mutating. There is no statement of when to prefer this over list-whatsapp-templates or get-gallery-template, and no prerequisites are mentioned.

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

Deploy Server

Other Tools