Skip to main content
Glama
Sign In

LinkMCP: hosted LinkedIn MCP server

by io.linkmcp
OverviewDiscussionsAdmin

List Conversations

linkedin_list_conversations
Read-onlyIdempotent

List the user's LinkedIn message conversations (inbox). Use this when the user asks about their LinkedIn messages: unread messages, who replied, replies from people at a company, or the conversation with one person. Returns conversation ID, timestamp, unread status, the other participant's provider ID, and the LinkedIn thread ID. Each conversation includes the other person's name, and their headline and profile link when LinkedIn provides them, so no profile lookup is needed to see who a conversation is with. Each conversation also includes its last message when LinkedIn provides it: the text (cut to 300 characters), the time, the sender's name and whether you sent it, so you can sort the inbox without opening each conversation. By default it lists your LinkedIn inbox; set inbox to sales_navigator to list your Sales Navigator inbox. Supports cursor-based pagination. Optionally search for conversations with a specific person by providing a participant identifier. To find replies from people at a company or within a period, list the conversations with after (and unread_only if needed) and read each person's headline and last message. Results come in pages: when has_more is true, more conversations exist; call again with the same arguments and cursor set to next_cursor. Pacing: each page of results counts toward a daily limit of inbox reads. To check for new messages, pass after with the time of your last check: such a call usually reads one page.

Input Schema

NameRequiredDescriptionDefault
afterNoOnly return conversations updated after this time (exclusive). ISO 8601 date or datetime, for example 2026-08-15 or 2026-08-15T09:30:00Z. A date or time without an offset is read as UTC.
inboxNoWhich inbox to list: classic (your LinkedIn messages, the default) or sales_navigator (your Sales Navigator messages; the connected LinkedIn account needs Sales Navigator). Use the same value with cursor.
limitNoNumber of conversations to return per page (1–250, default 20). Ignored when participant is provided.
beforeNoOnly return conversations updated before this time (exclusive). ISO 8601 date or datetime, for example 2026-08-15 or 2026-08-15T09:30:00Z. A date or time without an offset is read as UTC.
cursorNoPagination cursor from a previous response. Omit for the first page.
participantNoFind conversations with a specific person. Provide a LinkedIn profile URL, public ID, URN, or numeric ID. Each call scans only your most recent conversations to find matching threads. Other filters (unread_only, after, before) still apply. Use cursor to continue scanning if not found.
unread_onlyNoIf true, return only conversations with unread messages. If false, return only read conversations. Omit to return all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / inbox
      Added value: +{
+  "description": "Which inbox to list: classic (your LinkedIn messages, the default) or sales_navigator (your Sales Navigator messages; the connected LinkedIn account needs Sales Navigator). Use the same value with cursor.",
+  "enum": [
+    "classic",
+    "sales_navigator"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / participant / description
      Previous value: -"Find conversations with a specific person. Provide a LinkedIn profile URL, public ID, URN, or numeric ID. Scans up to 1250 recent conversations to find matching threads. Other filters (unread_only, after, before) still apply. Use cursor to continue scanning if not found."New value: +"Find conversations with a specific person. Provide a LinkedIn profile URL, public ID, URN, or numeric ID. Each call scans only your most recent conversations to find matching threads. Other filters (unread_only, after, before) still apply. Use cursor to continue scanning if not found."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations it discloses two non-obvious traits: a daily limit on inbox reads that each page consumes, and that participant search only scans recent conversations, requiring cursor to continue scanning. It also notes last-message text is truncated to 300 characters and that fields appear only 'when LinkedIn provides' them. It stops short of describing rate-limit numbers or failure modes, but the behavioral coverage is well above the annotation baseline.

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?

Front-loaded with purpose, then use cases, then return shape, then pagination and pacing – a sensible order. It runs long at eight sentences and a couple of clauses are justificatory filler ('so no profile lookup is needed', 'so you can sort the inbox'), but nothing is genuinely off-topic.

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?

Covers everything an agent needs for a 7-parameter, zero-required read tool with no output schema: what comes back per conversation, how paging terminates, how polling works, the quota cost, and the scan limit on participant search. No material gap remains.

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?

With 100% schema coverage the baseline is 3, but the description adds cross-parameter meaning the schema only states individually: switching inbox to sales_navigator, carrying the same inbox value alongside cursor, combining participant with unread_only/after/before, and using after as the polling anchor. These combinations are the practically hard part of calling this tool correctly.

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 the user's LinkedIn message conversations / inbox) and enumerates the concrete questions it answers (unread messages, who replied, replies from a company, one person's thread). It also distinguishes itself from reading messages by promising last-message text and participant headline so 'no profile lookup is needed' and the inbox can be sorted 'without opening each conversation.'

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 triggers tied to user phrasing, names the recipe for company/period reply hunting (list with after, optionally unread_only, then read headline and last message), and covers pagination continuation with the same arguments plus next_cursor. It even prescribes the polling pattern: pass after with the time of your last check, which usually reads one page.

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

All LinkMCP: hosted LinkedIn MCP server 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