Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

link_entities

Attach contacts or a company to an existing lead, or link other entities, to complete missing associations or fix a lead created without them.

Instructions

Attach contacts or a company to an existing lead (or link other entities). Use after create_lead when more contacts are needed, or to fix a lead created without them.

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": {
      "entity_id": "<entity_id>",
      "links": "<links>"
    },
    "name": "link_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYesEntities to attach, e.g. [{entity_type:'contacts', entity_id:123, is_main:true}]
entity_idYesID of the entity to attach TO (e.g. the lead ID)
entity_typeNoEntity to attach TO (default: leads)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves the important questions unanswered: whether links append or replace existing ones, what happens when an entity is already linked or does not exist, whether permissions on both sides are needed, and whether the operation is reversible. The only behavioral content is sequencing guidance relative to create_lead.

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 short sentences, front-loaded with the action and followed by the triggering condition. Nothing is redundant.

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 tool with nested link objects, two enums, and no annotations or output schema, the description covers what the tool does and when, but says nothing about failure modes, idempotency, or what a successful link returns. Adequate to attempt a call, not enough to predict its outcome.

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%, so the nested links array, entity_type enums, is_main flag, and the attach-TO semantics are already documented in the schema. The description's mention of 'contacts or a company' and 'more contacts' loosely maps to those fields but adds no format or constraint detail beyond the schema.

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 gives a specific verb and resource: 'Attach contacts or a company to an existing lead (or link other entities)'. The parenthetical broadens scope in a way that slightly dilutes the claim, and the inverse sibling unlink_entities is never named, so differentiation is implicit rather than explicit.

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 states clear usage context: use after create_lead when more contacts are needed, or to fix a lead created without them. There are no explicit exclusions or named alternatives, but the lifecycle framing is genuinely useful for choosing this tool over create_lead or update_lead.

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