Skip to main content
Glama
amocrm-mcp-prm

amocrm-mcp-prm

by m00zz

list_tasks

Retrieve and filter amoCRM tasks by entity, completion status, responsible user, or deadline range to find overdue work and manage follow-ups.

Instructions

List tasks in amoCRM. Filter by entity (lead/contact/company), completion status, responsible user, or deadline range (overdue tasks).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoItems per page (max 250, default 50)
due_toNoDeadline (complete_till) at or before this date. With is_completed=false and due_to=now this gives overdue tasks.
compactNoReturn a trimmed view with readable dates
due_fromNoDeadline (complete_till) at or after this date
entity_idNoFilter by entity ID (requires entity_type)
order_dirNoSort by deadline
entity_typeNoFilter by entity type
is_completedNoFilter by completion status
responsible_user_idNoFilter by responsible user

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?

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only that results are filterable and that overdue tasks can be isolated. It never states that this is a non-mutating read, how many results come back, or anything about pagination cost, though the schema's page/limit/order_dir give structural hints.

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, zero filler, and the core purpose is front-loaded ahead of the filter capabilities. Nothing is repeated or padded.

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?

With 10 parameters, no annotations, and no output schema, the definition should at least indicate that results are a task list and how paging/compact interacts with large result sets. The filter surface is adequately covered and the schema fills in the details, but the absence of any return-value or paging context leaves a noticeable gap for a tool with this many knobs.

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 explains every parameter, including the overdue-tasks recipe on due_to. The description restates the filter dimensions at a coarse level (entity, status, assignee, deadline) without adding syntax or value-format guidance, which is the baseline for full schema coverage.

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?

"List tasks in amoCRM" gives a specific verb (List) plus resource (tasks), and the second sentence enumerates the filterable dimensions. It implicitly separates itself from create_task/complete_task by being a read/query operation, though it never names a sibling alternative explicitly.

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?

Usage is implied by the filter list: use it to find tasks by entity, status, assignee, or deadline. The overdue-task use case is a helpful hint, but there are no stated exclusions, prerequisites, or pointers to alternatives such as search or complete_task.

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