Skip to main content
Glama

LinkedIn: List inbox chats

linkedin_list_inbox_chats
Read-onlyIdempotent

List chats from a specific LinkedIn inbox. Use for LinkedIn V2 and premium Sales Navigator/Recruiter inboxes; account-wide chat listing is unsupported. Get inbox_id from linkedin_list_inboxes. Pages are capped at 20; follow every cursor and list each intended inbox separately. A page is not an exhaustive digest. With cursor, the page size of the first page is kept (limit is ignored).

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
cursorNo
inbox_idYesExact LinkedIn inbox ID returned by linkedin_list_inboxes. Preserve Classic/Sales Navigator/Recruiter selection; never pass contract_id or product name. Inbox ID: Provider inbox/product inbox identifier. LinkedIn Classic may use CLASSIC; premium products expose their own inbox IDs. Obtain with: linkedin_list_inboxes -> inbox.id Never pass: contract_id unless returned as the inbox id, guessing SALES_NAVIGATOR or RECRUITER.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description focuses on non-obvious traits: 20-item page caps, the warning that a page is not an exhaustive digest, and the fact that passing a cursor locks the page size from the first page. It stops short of describing response shape or rate limits, but adds real behavioral value beyond the annotations.

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?

Five dense sentences, front-loaded with the core action and scope, then prerequisite, then pagination caveats. Every sentence carries operational information, though the cursor/page-size sentence is compressed enough to require careful parsing.

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 7-parameter listing tool with no output schema and thin schema descriptions, the definition covers the hard parts (inbox resolution, mandatory cursor following, per-inbox iteration) but leaves three filter parameters unexplained and never says whether the date bounds are inclusive or what a chat record contains. Adequate, not complete.

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?

With only 29% schema description coverage, the description must compensate: it explains cursor/limit interaction and the source of inbox_id, which is genuinely useful. However, `after`, `before`, and `is_unread` are given no meaning anywhere, and the stated 20-page cap sits in tension with the schema's limit maximum of 250 without clarifying how they relate.

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 and resource ("List chats from a specific LinkedIn inbox") and scopes it to a single inbox, which separates it from the account-wide conversation listings in the sibling set. It does not explicitly name linkedin_list_conversations as the account-wide alternative, leaving the agent to infer the routing.

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 conditions (LinkedIn V2 and premium Sales Navigator/Recruiter inboxes), an explicit exclusion (account-wide chat listing is unsupported), a prerequisite chain (get inbox_id from linkedin_list_inboxes), and procedural guidance (follow every cursor, list each inbox separately).

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.