PilotControl

Preparar una campaña de WhatsApp

whatsapp_create_campaign

Crea solo un borrador de campaña en PilotControl con una plantilla aprobada (template_id) y una lista existente (list_id) de la marca. No contacta WhatsApp ni envía mensajes. No se puede programar. Para enviarlo después usa whatsapp_send_campaign, que requiere confirmación. variables completa {{1}}, {{2}}… (por ejemplo {"1": "{{name}}"}). Repetir esta creación genera otro borrador.

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": {
      "name": "<name>",
      "template_id": "<template_id>",
      "list_id": "<list_id>",
      "connection_id": "<connection_id>",
      "account_id": "<account_id>"
    },
    "name": "whatsapp_create_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`list_id`	Yes
`brand_id`	No	ID de la marca (de list_brands). Usa solo la marca que el usuario nombró; si no la nombró y hay varias, pregúntale cuál.
`variables`	No
`account_id`	Yes
`template_id`	Yes
`connection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations it discloses that the result is only a local draft, that no WhatsApp traffic occurs, that scheduling is impossible, and that repeating the call produces a second draft — consistent with idempotentHint=false and destructiveHint=false. It does not mention permission or connection requirements, which a mutation tool would ideally state.

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

Conciseness4/5

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

The draft-only constraint and the sibling routing are front-loaded in the first two sentences, and each subsequent sentence adds new information. The variables clause is telegraphic ('variables completa {{1}}, {{2}}…') but still parses, so nothing is wasted.

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?

For a non-destructive draft-creation tool with no output schema, the description covers the essential behavior and the follow-up path. It falls short only on the roles of connection_id/account_id and on what the created draft looks like, which an agent would need to chain into whatsapp_send_campaign.

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?

With only 14% schema description coverage the description carries most of the burden; it usefully explains the variables map syntax with an example ({"1": "{{name}}"}) and the meaning of template_id/list_id. However, name, connection_id and account_id receive no semantic explanation anywhere, leaving a significant part of the 7 parameters undocumented.

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 states a precise verb and resource ('Crea solo un borrador de campaña en PilotControl') and narrows the scope to a template_id plus an existing brand list_id. It is immediately distinguishable from whatsapp_send_campaign and from the template/contact-list creation siblings.

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

Usage Guidelines5/5

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

It explicitly states the boundaries ('No contacta WhatsApp ni envía mensajes. No se puede programar') and names the correct follow-up tool with its precondition ('usa whatsapp_send_campaign, que requiere confirmación'). The when-not-to-use case for direct sending is covered by that routing sentence.

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

All PilotControl tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?