Skip to main content
Glama

Messaging: List chats

messaging_list_chats
Read-onlyIdempotent

List personal chats for WhatsApp, Instagram, Facebook or Telegram. For Facebook Pages use facebook_list_inboxes and facebook_list_inbox_chats; never fall back to the personal inbox. Chats are most recently active first; use it to find a chat_id. LinkedIn requires inbox-specific listing. V2 filters: type, before/after (on the chat's last activity), archived and unread; WhatsApp pages by offset, other providers by cursor. For 'messages received between X and Y' call messaging_list_recent_messages, which also reads the messages.

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": {
      "provider": "<provider>"
    },
    "name": "messaging_list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
afterNo
limitNo
beforeNo
cursorNo
offsetNo
providerYes
is_unreadNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
is_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "whatsapp",
      -  "instagram",
      -  "telegram"
      -]New value: +[
      +  "whatsapp",
      +  "instagram",
      +  "facebook",
      +  "telegram"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behaviour, and the description adds real context on top: ordering is 'most recently active first', before/after filter on last activity, and pagination differs by provider (WhatsApp by offset, others by cursor). It does not describe the returned chat fields, which matters somewhat since there is no output schema.

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?

Five tightly packed sentences with no filler; the core purpose and the Facebook Pages exclusion come first, followed by ordering, filtering and pagination details, then the cross-tool redirect. Nothing is repeated from the schema or title.

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 a 10-parameter, low-coverage, no-output-schema tool this covers routing, ordering, filters and pagination modes well. Remaining gaps are limit behaviour and the shape of returned chats, but an agent has enough to invoke it correctly.

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

Parameters4/5

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

Schema description coverage is only 10%, so the description must carry the load, and it largely does: it explains type, before/after semantics, archived and unread filters, and the provider-dependent offset vs cursor split. It leaves limit and the meaning/source of cursor values unexplained, so it falls short of full compensation.

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 personal chats') and bounds the scope to WhatsApp, Instagram, Facebook and Telegram. It explicitly distinguishes itself from the Facebook Pages siblings and from LinkedIn inbox-specific listing, so an agent can route without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use and when-not-to-use rules: 'For Facebook Pages use facebook_list_inboxes and facebook_list_inbox_chats; never fall back to the personal inbox', plus 'LinkedIn requires inbox-specific listing' and a redirect to messaging_list_recent_messages for date-range message retrieval. It names alternatives and the condition that selects each.

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.