Skip to main content
Glama
hajekd
by hajekd

list_messenger_chats

List Facebook Messenger chat activities from Daktela with filters for queue, agent, contact, direction, and date range, returning channel-specific fields.

Instructions

List Facebook Messenger activities with channel-specific fields.

Args: queue: Filter by queue internal name (e.g. '10333'). Use list_queues to find names. user: Agent name — pass either a display name (e.g. 'John Doe') or login name (e.g. 'john.doe'). Resolved automatically. contact: Filter by contact internal ID (e.g. 'contact_674eda46162a8403430453'). NOT a person's name — call list_contacts(search='...') first to find the ID. direction: Filter by direction: IN or OUT. date_from: Filter by activity start time on or after this date (YYYY-MM-DD). date_to: Filter by activity start time on or before this date (YYYY-MM-DD). sort: Field to sort by. Useful values: time, duration, wait_time. WARNING: only fields that exist on this endpoint work — do NOT use 'created' or 'edited'. sort_dir: Sort direction: asc or desc (default: desc). skip: Pagination offset (default: 0). take: Number of records to return (default: 50, max: 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo
sortNo
takeNo
userNo
queueNo
contactNo
date_toNo
sort_dirNodesc
date_fromNo
directionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context, including that 'contact' is not a person's name but an internal ID, that user names are resolved automatically, and a warning that sort fields must exist on the endpoint (avoiding 'created'/'edited'). These go beyond the schema and reveal important behavioral nuances.

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?

The description is structured as a concise one-liner followed by an Args section. Each parameter gets a clear, non-redundant line. Despite the length, every sentence serves a purpose, and the structure aids scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high parameter count and no annotations, the description is remarkably complete. It covers all parameters, includes practical examples, and highlights edge cases. The output schema exists, so return values do not need to be explained. The description leaves little ambiguity for an agent invoking this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining all 10 parameters with formats, examples, defaults, and warnings. For instance, it clarifies the difference between display name and login for 'user', and warns about sort field limitations.

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?

The description clearly states the tool lists 'Facebook Messenger activities with channel-specific fields', using a specific verb and resource. This distinguishes it from sibling tools like list_instagram_chats and list_whatsapp_chats.

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?

The description provides clear context for when this tool is appropriate (Messenger activities) and includes explicit cross-tool references, such as using list_queues to find queue names and list_contacts to find contact IDs. It does not explicitly mention alternatives to exclude, but the scope is well-defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hajekd/mcp-daktela'

If you have feedback or need assistance with the MCP directory API, please join our Discord server