Skip to main content
Glama

kommo_talks_list

Read-onlyIdempotent

Conversas (talks) do inbox unificado. action: list (filtrável por contact_id/entity_id/only_in_work via filter JSON) | get (por id). Para ler o texto das mensagens, use kommo_talks_messages.

[Flattened action: list]

Bulk support: accepts ids for batched execution.

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": "kommo_talks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
idsNo
pageNo
limitNo
filterNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so safety is covered. The description adds genuine value by disclosing bulk support via `ids`, but says nothing about pagination behavior (page/limit), result size, or what a talk record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact, but the structure is muddled: it mixes list and get semantics in one definition, carries an internal artifact ('[Flattened action: list]'), and the bulk-support sentence is appended after the routing advice, so the reading order is not cleanly front-loaded.

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?

There is no output schema, yet the description never characterizes the returned talk objects, and pagination parameters go unexplained. For a six-parameter read tool the routing advice and filter key hints are helpful, but an agent still lacks enough to call it confidently with paging.

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 0%, so the description carries full burden. It explains the `filter` JSON keys and the bulk `ids` mechanism and implies `id` for the get path, but leaves `page`, `limit`, and `account` completely undocumented in both schema and description.

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 resource (talks/conversations from the unified inbox) and the listing operation, and names kommo_talks_messages as the tool for message bodies. However, it also describes a 'get (por id)' mode even though a sibling kommo_talks_get exists, which muddies what this specific tool does versus its siblings.

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 filtering context (filterable by contact_id/entity_id/only_in_work via the `filter` JSON) and an explicit routing rule: to read message text, use kommo_talks_messages. It does not state when the standalone get mode should be used instead of kommo_talks_get, leaving one sibling relationship ambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.