Skip to main content
Glama
Sign In
WACrew

WACrew

by sumioshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

editar_perfil

Update your WhatsApp profile name, status text, or photo by sending only the fields you want to change. Preview the changes and get operator approval before publishing, since the profile is public.

Instructions

Edita o PERFIL do WhatsApp do operador: nome, recado/'sobre' (status) e/ou foto. Passe só os campos que quer mudar. 'foto' é caminho absoluto de imagem OU o mediaPath de uma mensagem recebida. CONFIRMAÇÃO: o perfil é PÚBLICO (todo contato vê). Você DEVE mostrar ao operador o que vai mudar e ter o OK ANTES de chamar — mesma convenção do 'responder'. Não é trava de código; não burle. LIMITE: catálogo, localização, link e horário-oficial do business são read-only no WhatsApp (não editáveis por aqui).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "editar_perfil"
  }
}

Input Schema

NameRequiredDescriptionDefault
fotoNocaminho absoluto de uma imagem OU mediaPath relativo (de uma mensagem recebida)
nomeNonovo nome do perfil (push name)
recadoNonovo recado/'sobre' (status do perfil)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the profile is PUBLIC and visible to every contact, requires explicit operator confirmation before invocation, and notes this is a social convention rather than a code lock. It omits what the tool returns and whether omitting a field leaves it untouched versus clearing it, so there is still a gap for a mutation tool with no output schema.

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?

Front-loaded with what the tool does, then a scoping rule, then the confirmation requirement, then the read-only limits — each sentence adds a distinct constraint. No filler or restatement of the tool name.

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 3-optional-parameter mutation tool with zero annotations and no output schema, the description covers safety, merge semantics, and non-editable fields well. The remaining shortfall is the absence of any indication of what a successful call returns or how failures surface.

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 already 100%, so the baseline is 3; the description goes beyond by clarifying that 'foto' accepts either an absolute image path or the mediaPath of a received message, and that only the supplied fields are mutated. Those two clarifications change how an agent would populate the parameters, not just restate them.

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?

States a concrete verb and resource ("Edita o PERFIL do WhatsApp do operador") and enumerates the exact editable facets: nome, recado/'sobre', foto. The resource (profile, not messages or chats) makes it unmistakable against siblings like editar_mensagem even without naming them.

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?

Explicitly says to pass only the fields being changed (partial-update guidance) and adds a clear exclusions list: catálogo, localização, link e horário-oficial do business are read-only and cannot be changed here. It also imposes a pre-call workflow (show the operator the diff, get OK), which is a real usage rule rather than vague context.

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