Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_events

Retrieve amoCRM activity events newest first, filtering by entity, event type, date range, author, and status to inspect changes, calls, and notes.

Instructions

List events (activity log) in amoCRM, newest first. Filter by entity, event type(s), date range, author, and target/source status. Shows status changes, calls, notes, and other activities. For stage-move counts over a period use status_transitions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
typeNoFilter by event type (e.g. 'lead_status_changed', 'incoming_call', 'entity_linked')
limitNoItems per page (max 100, default 50)
typesNoFilter by several event types at once
entityNoFilter by entity type
entity_idNoFilter by specific entity ID
created_byNoFilter by user IDs who triggered the event
created_toNoEvents at or before this date
created_fromNoEvents at or after this date
status_afterNoFor lead_status_changed: only moves INTO these statuses
status_beforeNoFor lead_status_changed: only moves OUT OF these statuses

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 full burden. It does disclose useful behavior — result ordering (newest first) and the kinds of activities returned (status changes, calls, notes, other activities) — but says nothing about pagination limits, result caps, or permission/auth requirements for a read-heavy log tool.

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?

Three sentences, front-loaded with what the tool returns and its ordering, followed by filter scope and the sibling exclusion. No redundant or filler wording; each sentence adds 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?

For an 11-parameter, zero-required, no-output-schema read tool with no annotations, the description covers purpose, ordering, filter surface, and the main alternative. The remaining gap — paging defaults and result limits — is handled in the schema, so an agent has enough to call it correctly.

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 baseline is 3. The description's summary of filter dimensions ('entity, event type(s), date range, author, and target/source status') loosely maps to the parameters, but it adds no syntax, format, or default details beyond what the schema already documents for status_before/status_after, created_from/created_to, page, and limit.

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 ('List events (activity log) in amoCRM') plus a defining behavior ('newest first'), and clarifies scope against a named sibling by deferring stage-move counting to status_transitions. An agent can pick this tool over status_transitions without opening either 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 an explicit routing rule: 'For stage-move counts over a period use status_transitions,' which tells the agent when this tool is the wrong choice. It stops short of contrasting with other list-style siblings such as list_notes, but the primary ambiguity is resolved.

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