Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

update_contact

Updates an existing contact by ID, changing name, responsible user, or custom fields such as phone and email.

Instructions

Update an existing contact: name, responsible user, or custom fields (phone, email).

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

Input Schema

NameRequiredDescriptionDefault
nameNoFull contact name
last_nameNoLast name
contact_idYesContact ID to update
first_nameNoFirst name
responsible_user_idNoNew responsible user ID
custom_fields_valuesNoCustom field values to set (phone, email, etc.). Replaces the listed fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

C2.9/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 for a mutation tool. It never says whether updates are partial or full-replace, whether omitted fields are preserved, whether permissions/ownership rules apply, or what failure looks like — all significant gaps for a write operation.

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?

A single front-loaded sentence with no filler and the resource/operation stated first. It is efficient, though the colon-separated field list reads slightly like a schema restatement rather than purpose-driven guidance.

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

Completeness2/5

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

With six parameters, no annotations, and no output schema, the description should explain update semantics (partial vs replace), the required contact_id, and mutation side effects. None of that is present, leaving the definition materially incomplete for a write tool.

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 schema already documents every parameter, and description-vs-schema parity is at the baseline. The description usefully groups 'name' as covering first/last name but adds no syntax, format, or constraint details beyond the schema, and the schema's important 'Replaces the listed fields' semantic is not echoed or clarified.

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?

States a specific verb (update) and resource (contact) plus the categories of fields that can change, so it is clearly distinguishable from create_contact and get_contact by name alone. It stops short of explicitly naming a sibling/alternative, keeping it below a 5.

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 word 'existing' weakly implies this is not for creating records, but there is no explicit when-to-use, no prerequisite (e.g., a valid contact_id), and no pointer to create_contact for new records or update_company for company records.

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