Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

create_lead

Add a new amoCRM deal with a required name, then set price, pipeline, status, tags, custom fields, or link/create a contact and company in one call.

Instructions

Create a new lead (deal) in amoCRM. Requires a name. Optionally set price, pipeline, status, responsible user, custom fields and tags. Can link an existing contact/company (contact_id, company_id) or create a new contact and company in the same call (contact, company) — uses the complex endpoint, one contact and one company per lead.

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

Input Schema

NameRequiredDescriptionDefault
nameYesLead name
tagsNoTag names to attach
priceNoLead budget/price
companyNoCreate a NEW company together with the lead (ignored when company_id is set)
contactNoCreate a NEW contact together with the lead (ignored when contact_id is set)
status_idNoStatus ID within the pipeline
company_idNoLink an EXISTING company
contact_idNoLink an EXISTING contact as the main contact
pipeline_idNoPipeline ID
responsible_user_idNoResponsible user ID
custom_fields_valuesNoCustom field values

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden for a mutation tool. It does add real behavior beyond the schema: the call uses the complex endpoint, nested entities are created atomically with the lead, and only one contact and one company are allowed per lead. It says nothing about required permissions, duplicate handling, what happens when both contact_id and contact are supplied, or failure/partial-write behavior.

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?

Front-loaded with purpose and the required field, then flows into optional parameters and finally the contact/company modes, which is the right order for an agent. The middle sentence enumerating price, pipeline, status, responsible user, custom fields and tags largely restates the schema and could be trimmed.

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 an 11-parameter tool with nested objects, no annotations and no output schema, the description covers the shape of the call and the nested-entity modes well. It does not tell the agent what comes back (a lead ID? the created contact IDs?), which matters because there is no output schema to consult, nor does it cover error or permission behavior.

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 the schema already documents every parameter and the baseline is 3. The description still adds meaning on top of it by framing the contact/company parameters as two mutually exclusive modes and by stating the 'one contact and one company per lead' cardinality limit, which the schema does not express.

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 ('Create a new lead (deal) in amoCRM') and immediately adds the required-field rule. It also distinguishes itself from the create_contact/create_company siblings by noting it can create a contact and company inline, so an agent can tell the tools apart 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?

Gives explicit guidance on the key decision an agent faces: link an existing contact/company via contact_id/company_id versus creating new ones via the nested contact/company objects. It also states the hard constraint 'one contact and one company per lead'. It does not say when to prefer update_lead over this tool, so it stops short of full when/when-not coverage.

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