Skip to main content
Glama

Move a lead between pipelines

crm_move_lead_to_branch

Move the lead out of one pipeline into another (entry stage, or to_stage_id of the destination). Reversible.

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>",
      "from_branch_id": "<from_branch_id>",
      "to_branch_id": "<to_branch_id>"
    },
    "name": "crm_move_lead_to_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLead id (UUID)
to_stage_idNoA stage of the destination (crm_list_stages branch=<to>)
to_branch_idYes"general" or the destination branch id
from_branch_idYes"general" or the branch id it leaves
assignee_user_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the operation is reversible and that the destination stage defaults to the entry stage, which is real behavioral context. It does not cover permission requirements, whether the lead remains in the source branch, or what the response contains.

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?

A single compact sentence with the core action and the to_stage_id override parenthetically attached. Nothing is wasted and the key behavior is front-loaded.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations and no output schema, the description covers the essential mechanics but leaves gaps: side effects on the source branch, assignee_user_id, and error/permission behavior. It is adequate but not 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 80%, so the baseline is 3, and the description genuinely adds meaning: it explains that to_stage_id is optional and defaults to the destination's entry stage, which the schema does not state. The only undocumented parameter, assignee_user_id, is left unexplained in both places.

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 names a specific verb (move) and resource (lead) and scopes it to branch/pipeline transfer, which separates it from stage-only movement. It stops short of explicitly naming how it differs from close siblings like crm_add_lead_to_branch or crm_move_lead, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The description implies the use case (taking a lead out of one pipeline and putting it into another) but never states when to pick this over crm_add_lead_to_branch, crm_move_lead, or reassign_crm_lead. With several near-identical siblings in the toolset, this omission forces the agent to infer the routing.

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