Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_custom_fields

Retrieves custom field definitions for leads, contacts, or companies, including IDs, types, and enum options, so you can set custom field values or group lead summaries by a field.

Instructions

List custom fields of leads, contacts, or companies with IDs, types and enum options. Needed to set custom_fields_values or to group leads_summary by a field.

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_type": "<entity_type>"
    },
    "name": "list_custom_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_typeYesEntity whose custom fields to list

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?

No annotations are supplied, so the description carries the burden. It discloses the return shape (IDs, types, enum options), which is genuinely useful, but says nothing about permissions, pagination, or whether the field list varies per account. Adequate for a simple read, with gaps.

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, front-loaded with the action and return payload, then the usage rationale. No filler or redundancy.

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 one-parameter read tool with full schema coverage and no output schema, the definition covers purpose, return contents, and use cases. Only minor behavioral details (auth, pagination) are absent.

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% and the single entity_type parameter has an enum with its own description, so the schema already does the work. The description restates the three entity options but adds no format or edge-case detail beyond the schema.

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 (list) and resource (custom fields) scoped to three entity types, and even names the returned fields (IDs, types, enum options). This clearly distinguishes it from siblings like list_leads or list_contacts, which return records rather than field metadata.

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 concrete downstream use cases: needed to set custom_fields_values or to group leads_summary by a field. That tells the agent when to reach for it. It stops short of naming an explicit alternative or exclusion, but the trigger conditions are clear.

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