Reach MCP

list_user_posts

Read-onlyIdempotent

Get recent posts published by a LinkedIn member (via profileUpdatesV2). Paginate with start/count. Use to read what a member published recently (their content, not who engaged); to get likers and commenters of a post use scrape_post. Read-only.

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>",
      "linkedin_id_or_url": "<linkedin_id_or_url>"
    },
    "name": "list_user_posts"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of posts (max 50).
`start`	No	Pagination offset.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`linkedin_id_or_url`	Yes	LinkedIn member ID, vanity name, or profile URL.

Output Schema

Name	Required	Description	Default
`posts`	No
`total_posts`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered and the trailing 'Read-only' adds nothing. The description does add useful behavior: pagination via start/count and the underlying endpoint. No mention of result caps beyond the schema or rate limits.

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 pagination mechanics, then the sibling disambiguation. Three tight sentences with almost no waste, though the trailing 'Read-only.' duplicates the readOnlyHint annotation and could be dropped.

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 paginated read tool with an output schema (so return values need no explanation) and full annotation coverage, the description supplies purpose, pagination, and alternative routing. Only minor gaps remain around result limits and the self-profile case.

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 description coverage is 100% (count max 50, start offset, account_id origin, linkedin_id_or_url formats), so the schema carries the parameter burden. The description only hints at pagination with 'Paginate with start/count,' adding no syntax or constraint detail beyond the schema; 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?

States a specific verb and resource (recent posts published by a LinkedIn member), including the underlying source profileUpdatesV2, and explicitly distinguishes the scope from engagement data. An agent can separate it from scrape_post and scrape_my_posts without opening any schema.

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?

Explicitly names the alternative for a different need: 'to get likers and commenters of a post use scrape_post,' which is a clear when-not statement. It does not address the closely related sibling scrape_my_posts (same data for the authenticated user), so routing is clear but not exhaustive.

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

All Reach MCP 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?