Skip to main content
Glama

Add a lead to another pipeline

crm_add_lead_to_branch

Place the lead in another pipeline too (entry stage); it stays in its current ones. Reversible via crm_move_lead_to_branch.

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>",
      "branch_id": "<branch_id>"
    },
    "name": "crm_add_lead_to_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLead id (UUID)
branch_idYes"general" or a branch id from crm_list_all_branches
assignee_user_idNoOwner in that pipeline (default: current owner)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers the two traits that matter most for a mutation: the operation is additive (existing pipeline memberships survive) and it is reversible via a named tool. It omits permissions/authorization needs and undefined edge behavior (lead already in that branch), which keeps it from a 5.

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?

Two sentences, no filler, and the add-vs-move distinction is front-loaded in the first clause. Every phrase ('too', 'entry stage', 'stays in its current ones', 'Reversible via...') carries distinct information.

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-parameter mutation with no annotations and no output schema, the description covers the essential semantics an agent needs to call it safely. Remaining gaps: no return-value indication and no statement of what happens on a duplicate add — modest for such a narrow operation.

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?

Schema description coverage is 100%: id, branch_id (with the 'general' or crm_list_all_branches guidance) and assignee_user_id (with its default) are all documented in the schema. The description's 'entry stage' adds context about where the lead lands but says nothing extra about any of the three parameters, so the baseline 3 applies.

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+resource (place the lead in another pipeline) plus the critical scope qualifier ('too') and the entry-stage position. It explicitly contrasts with the sibling crm_move_lead_to_branch, so an agent can distinguish the additive tool from the moving one without opening a 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?

The word 'too' plus 'it stays in its current ones' tells the agent the use-case: additive assignment rather than relocation. It also names crm_move_lead_to_branch as the reversal path, giving an alternative. It does not state a negative rule (e.g. use move instead when the lead should leave its current pipelines), so it falls short of a full 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