Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

unlink_entities

Detach contacts or companies from a lead without deleting them. Use it to unlink related entities by ID while keeping the original records intact.

Instructions

Detach contacts or a company from a lead (or unlink other entities). The detached entities are not deleted.

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": "unlink_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksYesEntities to detach
entity_idYesID of the entity to detach FROM
entity_typeNoEntity to detach FROM (default: leads)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it usefully discloses that detached entities are not deleted — the key safety fact for a destructive-sounding operation. It does not state whether unlinking is reversible, what permissions or preconditions apply (e.g., the lead must already be linked), or whether partial failures on a multi-item links array roll back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the core operation leads. The trailing parenthetical is the only low-value fragment.

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 3-parameter mutation with no annotations and no output schema, the description covers the essential non-deletion guarantee but leaves the agent uninformed about return behavior (whether unlinked entities are echoed back) and failure semantics. Adequate to invoke correctly in the happy path, incomplete around edge cases.

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 description coverage is 100%, so field-level meaning is already documented, and the description reinforces the directional semantics ("detach FROM") that matter for entity_id versus the links array. It adds orientation but no syntax or cardinality 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?

A specific verb ("Detach") plus a named resource relationship ("contacts or a company from a lead") tells the agent exactly what the tool does as the inverse of link_entities. The parenthetical "(or unlink other entities)" is vaguer and slightly dilutes the otherwise precise statement.

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

Usage Guidelines3/5

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

Usage is only implied through the inverse relationship with link_entities; there is no explicit statement of when to reach for this tool versus relinking or updating an entity. The "(or unlink other entities)" clause offers no condition that would guide selection among alternatives.

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