Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: List inbox chats

facebook_list_inbox_chats
Read-onlyIdempotent

List one explicitly selected personal or Page inbox by cursor. Keep full Page chat IDs and enumerate every requested inbox; this is one page, not an exhaustive digest.

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": {
      "inbox_id": "<inbox_id>"
    },
    "name": "facebook_list_inbox_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
afterNo
limitNo
beforeNo
cursorNoOpaque next_cursor from the previous page of this same account, identity and resource. No offset pagination.
inbox_idYesExact inbox.id from facebook_list_inboxes, including PAGE_<page_id>_INBOX for a selected Page. Not a Page profile_id or connection account_id.
is_unreadNo
account_idNoOwned Facebook unipile_account_id from list_connected_accounts. Not a Facebook person or Page ID. Required when several Facebook accounts exist.
is_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, lowering the bar. The description adds genuine context beyond them: results are a single cursor page, not an exhaustive digest, and Page chat IDs must be preserved. It does not describe return item shape, ordering, or rate-limit behavior, so it is useful but incomplete.

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

Conciseness4/5

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

Two dense sentences with the scope statement front-loaded; nothing is wasted. The second clause ('Keep full Page chat IDs and enumerate every requested inbox') is slightly compressed to the point of being cryptic, but overall it is tight.

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?

For a read-only list tool with no output schema, the description covers the pagination model but leaves the return shape and most filter parameters (type, unread, archived, limit) unaddressed. Adequate minimum viability, with clear gaps given the low schema description coverage.

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

Parameters2/5

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

Schema coverage is only 33% across 9 parameters. The description adds nothing about type, limit, is_unread, is_archived, before, or after beyond the schema's bare enum/types, and its only parameter-adjacent claim ('by cursor') repeats what the cursor schema field already says.

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 verb (list) and resource (chats in one selected personal or Page inbox), with explicit scope ('one page, not an exhaustive digest'). It implicitly separates itself from facebook_list_inboxes by saying the inbox must be explicitly selected, but never names that sibling outright, so it falls short of a 5.

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?

The phrase 'one explicitly selected personal or Page inbox' implies you must first obtain an inbox via facebook_list_inboxes, and the pagination caveat tells you to page rather than expect a full digest. However, it never says when to choose this over facebook_list_recent_messages or facebook_get_chat, and gives no exclusions.

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

All Nilyo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources