Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_notes

Read and filter CRM notes for leads, contacts, or companies—manager comments, call logs, SMS, and service messages—newest first, or scan all entities by date range.

Instructions

Read notes on a lead, contact, or company: manager comments, call logs with results and recording links, SMS, service messages. Newest first. Omit entity_id to scan notes across all entities for a date range.

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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the raw API response instead of the compact view
pageNoPage number (default 1)
limitNoItems per page (max 250, default 50)
entity_idNoEntity ID. Omit to list notes across all entities of this type (combine with a date range).
order_dirNoSort by update time (default desc: newest first)
note_typesNoFilter by note types: common (manager comments), call_in/call_out (calls), sms_in/sms_out, service_message, attachment
updated_toNoNotes updated at or before this date
entity_typeYesEntity type the notes belong to
updated_fromNoNotes updated at or after this date

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, the description carries the full burden; 'Read' signals a non-mutating operation and 'Newest first' discloses default ordering plus the payload shape (recording links, call results). It says nothing about permissions, whether history is truncated, or rate limits, so the behavioral profile is only partially covered.

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?

Three short sentences, front-loaded with what a note is before the scanning rule. Nearly every clause earns its place, though 'Newest first' and the entity_id tip duplicate schema text rather than adding new information.

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?

With nine parameters and no output schema, the description compensates by describing the returned content types and default ordering. Pagination and filters are covered by the schema, so remaining gaps (permissions, result volume) are minor for a read 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 coverage is 100%, so every parameter including entity_id omission, order_dir, and the note_types enum is already documented. The description largely restates those ('Newest first', omit entity_id to scan), adding little syntax or format meaning 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?

States a specific verb and resource ('Read notes') scoped to leads, contacts, or companies, and enumerates what a note contains (manager comments, call logs with results and recording links, SMS, service messages). No sibling is named, but the read-only framing makes it distinguishable from add_note without inference.

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?

Gives one concrete mode instruction: omit entity_id to scan notes across all entities for a date range. It does not say when to prefer this over get_lead_full or list_tasks, so the guidance is partial rather than a full when/when-not map.

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