Reach MCP

scrape_post

Read-onlyIdempotent

Fetch likers and/or commenters for a LinkedIn post. Pass the full post URL or slug. Set liked=true and/or comments=true. Use to get the people who liked or commented on one post you have the URL of; for the account's own recent posts use scrape_my_posts. Counts against the imports 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>",
      "post_id_or_url": "<post_id_or_url>"
    },
    "name": "scrape_post"
  }
}

Input Schema

Name	Required	Description
`liked`	No	Include likers.
`comments`	No	Include commenters.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`post_id_or_url`	Yes	LinkedIn post URL (incl. lnkd.in short links) or slug.

Output Schema

Name	Required	Description	Default
`items`	No
`post_id`	No
`total_likes`	No
`total_comments`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedOutput schema / $defs / LinkedInPostEngagerOut / properties / author_type

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "``member`` or ``company`` (a page commenting or reacting: full_name is the page name, linkedin_id its company id).",
+  "title": "Author Type"
+}

addedOutput schema / $defs / LinkedInPostEngagerOut / properties / linkedin_public_id / description
```
Added value: +"Member vanity name, or the page's for a company."
```

Changed1 schema field changedOct 4, 2026

changedInput schema / properties / post_id_or_url / description

Previous value: -"LinkedIn post URL or slug."New value: +"LinkedIn post URL (incl. lnkd.in short links) or slug."

First observedSep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: the quota consumption and that the operation is scoped to a single known post URL. It does not discuss result volume, limits, or failure modes, so it stops short of a 5.

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?

Three short sentences, front-loaded with the action and ending with the cost warning in the right place. Slight redundancy between 'Fetch likers and/or commenters for a LinkedIn post' and 'get the people who liked or commented on one post' costs it a point.

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?

An output schema exists, so return-shape explanation is not required, and the description covers scope, alternatives, parameter intent, and quota cost. It says nothing about result caps, pagination, or whether this works for company pages vs. personal posts, which are the remaining gaps for an open-world scraper.

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?

Schema coverage is 100%, giving a baseline of 3. The description goes beyond it by telling the agent to 'Set liked=true and/or comments=true' — clarifying that the two booleans default to false and that at least one must be enabled to get anything back — and by reinforcing that the identifier may be a full URL or slug.

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+resource pair: 'Fetch likers and/or commenters for a LinkedIn post.' It also names the sibling it is not ('for the account's own recent posts use scrape_my_posts'), so an agent can route between the two without opening either schema.

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?

Explicitly states the selecting condition ('one post you have the URL of') and names the alternative tool (scrape_my_posts) with the condition that selects it. It also discloses the cost side-effect ('Counts against the imports quota'), which is a genuine when-to-use consideration.

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?