Skip to main content
Glama

Move contacts

move_contacts
Destructive

Move VÁRIOS contatos de uma vez para uma etapa (inclusive de outro funil), com o mesmo efeito de mover um a um: grava o histórico de etapas e dispara os gatilhos de etapa (automações, processo de ganho). Escolha quem move por contact_ids OU por de_funil + de_etapa (opcionalmente só quem tem a etiqueta). Até 500 por chamada; quem já está na etapa de destino é pulado. Use para levar uma lista inteira para o funil de prospecção ou passar os qualificados ao comercial.

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": {
      "para_etapa": "<para_etapa>"
    },
    "name": "move_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoMáximo de contatos (padrão e teto 500).
de_etapaNoEtapa de origem (nome exato). Com de_funil, move todos os contatos dela.
de_funilNoFunil de origem (id ou nome).
etiquetaNoSó os contatos com esta etiqueta (opcional, junto com de_etapa).
para_etapaYesEtapa de destino (nome exato).
para_funilNoFunil de destino (id ou nome). Obrigatório quando o nome da etapa existe em mais de um funil.
contact_idsNoIDs separados por vírgula ou array JSON. Alternativa a de_funil + de_etapa.

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 flag destructiveHint=true and readOnlyHint=false, and the description adds real behavioral context beyond that: it writes stage history, fires stage triggers (automations, win process), caps at 500 per call, and silently skips contacts already in the target stage. Those side effects and the skip rule are exactly what an agent needs before a destructive bulk write.

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 front-loaded sentences: effect and scope first, then how to select targets, then limits and skipping behavior. No filler, and the cap and skip rule are placed where an agent will read them before invoking.

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 7-parameter destructive bulk mutation with no output schema, the description covers side effects, limits, selection modes, and skip behavior. It does not describe what is returned (e.g., counts of moved versus skipped contacts), which would be useful given there is no output schema, so it is strong but not fully complete.

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 the baseline is 3, but the description adds the either/or semantics between contact_ids and de_funil + de_etapa, notes the optional tag filter in combination with de_etapa, and states that contacts already at the destination are skipped. That clarifies how parameters interact rather than merely restating field docs.

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 specific verb and resource — move multiple contacts at once to a stage, including across pipelines — and explicitly contrasts it with moving one at a time. The bulk scope and the 'inclusive de outro funil' qualifier let an agent tell it apart from any single-contact or list tool without opening the schema.

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?

Gives concrete when-to-use scenarios ('levar uma lista inteira para o funil de prospecção ou passar os qualificados ao comercial') and explains the two selection modes (contact_ids vs de_funil + de_etapa). It does not state when NOT to use it or name an alternative tool, so it stops short of full routing guidance.

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