Skip to main content
Glama

Set whatsapp number use

set_whatsapp_number_use
DestructiveIdempotent

Define para que serve um número de WhatsApp da conta (Minha Conta > WhatsApp): uso "empresa" (atendimento e vendas, com agente), "marca" (outro negócio, com caixa e cor próprias) ou "pessoal" (só registra: só quem conectou o número vê as conversas, a IA nunca responde e nada entra em automação, cadência, funil, metas, relatórios nem no MCP de outras pessoas). Também troca o nome (o da caixa nas Conversas) e a cor do selo. Só quem conectou o número pode marcá-lo como pessoal.

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": {
      "numero": "<numero>"
    },
    "name": "set_whatsapp_number_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
corNoCor do selo em hex (#rrggbb). Vazio = automática.
usoNoPara que serve o número
nomeNoNome do número na caixa das Conversas (até 30 letras, ex.: "Seu Lima", "Pessoal")
numeroYesid do número ou o nome dele (ver get_whatsapp_status → numeros)
target_user_idNo(Só o admin da plataforma) userId da conta a operar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them by spelling out the consequences of the "pessoal" mode: only the connector sees the conversations, the AI never responds, and nothing flows into automation, cadence, funnel, goals, reports or other users' MCP. It also discloses the permission constraint, which is exactly the kind of context annotations cannot express.

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 main purpose is front-loaded in the first clause and the enum explanations follow in a logical order, with the permission caveat last. The long parenthetical list for "pessoal" is dense but every element is substantive rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, idempotent mutation with no output schema, the description covers the purpose, the enum semantics, the side effects on downstream systems, and the authorization constraint. An agent has enough to decide whether to call it and what the outcome will be.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 applies, but the description adds genuine meaning by expanding each enum value ("empresa" = atendimento e vendas com agente, "marca" = outro negócio com caixa e cor próprias, "pessoal" = apenas registro) beyond the schema's bare "Para que serve o número". It also clarifies that "nome" is the name shown in the Conversas inbox, so the parameter layer is meaningfully enriched.

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 opens with a specific verb and resource: "Define para que serve um número de WhatsApp da conta", and then names the three concrete usage modes plus the secondary effects (renomear e cor do selo). This clearly separates it from siblings like set_brand or set_business_summary, which configure other account attributes.

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

Usage Guidelines4/5

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

It gives clear context for when the tool applies and states a real prerequisite: "Só quem conectou o número pode marcá-lo como pessoal", plus points to get_whatsapp_status → numeros for resolving the number identifier. It does not name an explicit alternative tool for other configuration tasks or state when NOT to use it, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources