Reach MCP — LinkedIn for AI agents

star_conversation

Idempotent

Star or unstar a LinkedIn conversation. Set star=false to remove the star. conversation_linkedin_id is the conversation_id returned by list_conversations; with page_id, a conversation of that company page's inbox. Housekeeping in the classic inbox or, with page_id, a company page's inbox; reversible (star=false). No quota.

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": {
      "account_id": "<account_id>",
      "conversation_linkedin_id": "<conversation_linkedin_id>"
    },
    "name": "star_conversation"
  }
}

Input Schema

Name	Required	Description
`star`	No	True to star, False to unstar.
`page_id`	No	Act as this company page instead of the member: page_id (or vanity name) from list_managed_pages. The account must be an admin of the page with a role that allows the action. Omit to act as the member.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`idempotency_key`	No	Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedIn. Reusing a key with different arguments is refused. Keys expire after 24 hours.
`conversation_linkedin_id`	Yes	Conversation (thread) id, as returned by list_conversations.

Output Schema

Name	Required	Description	Default
`starred`	No	Current starred state

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / page_id

Added value: +{
+  "description": "Act as this company page instead of the member: page_id (or vanity name) from list_managed_pages. The account must be an admin of the page with a role that allows the action. Omit to act as the member.",
+  "type": "string"
+}

First observedSep 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations it discloses that the action is reversible via star=false and that it consumes 'No quota' – meaningful given the quota tools in this sibling set. It does not repeat idempotency, which annotations already cover, so the added context is genuine rather than redundant.

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

Conciseness3/5

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

The core operations are front-loaded, but the second half is a semicolon-chained fragment ('Housekeeping in the classic inbox or...; reversible (star=false). No quota.') that reads as notes rather than prose. The star=false behavior is stated twice, once in the first and once in the third sentence.

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 simple boolean toggle with an output schema, full parameter coverage, and clear annotations, the description supplies what an agent needs: the operation, the reversal path, and the quota impact. Nothing critical is missing, though a note on which inbox context is typical would round it out.

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?

Schema coverage is 100% and the description largely restates it: 'star=false' duplicates the star property's 'True to star, False to unstar,' and 'conversation_linkedin_id is the conversation_id returned by list_conversations' duplicates the schema's own wording. The page_id explanation adds nothing the schema lacks, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Star or unstar a LinkedIn conversation,' and states the reverse operation inline. That clearly separates it from siblings like archive_conversation and delete_conversation, which act on the same object with different outcomes.

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?

It frames the operation as 'housekeeping in the classic inbox or, with page_id, a company page's inbox,' which tells the agent the contexts where this applies and the page-scoped variant. It stops short of naming alternatives such as archive or delete for cleanup, leaving the agent to infer when starring is preferable.

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

All Reach MCP — LinkedIn for AI agents tools Inspect

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

Need Help?