Reach MCP

scrape_my_posts

Read-onlyIdempotent

Fetch likers and/or commenters for the account's own recent posts. since_hours limits to posts published in the last N hours (default 24). Use for engagement on the account's own posts (likers, commenters, comment URNs for reply_comment); for someone else's post use scrape_post.

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

Input Schema

Name	Required	Description
`liked`	No	Include the people who liked.
`comments`	No	Include the people who commented, with their comment text.
`max_posts`	No	Max posts to process (max 20).
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`since_hours`	No	Only posts from the last N hours (max 720).

Output Schema

Name	Required	Description	Default
`posts`	No
`total_posts`	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."
```

First observedSep 10, 2026

TDQS

A4.1/5.0

Behavior3/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 carried by structured data. The description adds real context beyond that: the data is restricted to the caller's own account, since_hours defaults to 24 hours, and comment URNs are returned specifically so reply_comment can consume them. It does not mention quota consumption, the 20-post ceiling, or rate limits, which matter for an open-world scraping tool.

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 what the tool does, then the scoping parameter, then routing to the alternative. The middle clause restating since_hours and its default duplicates the schema and is the one mildly expendable element.

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?

With rich annotations, a fully described input schema, and an output schema that needn't be explained, the remaining burden is scope and routing, both covered. Minor gaps are operational: no note on quota/cost of an open-world scrape or on how the 20-post cap and since_hours interact when few posts match.

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%, so all five parameters are already documented, including defaults for liked, comments, max_posts, and since_hours; the baseline is therefore 3. The description only restates the since_hours window and default, and adds marginal semantic value by clarifying that the comments output includes replyable URNs, but it contributes no meaning for liked, max_posts, or account_id beyond the schema.

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 ("Fetch likers and/or commenters") with an explicit scope constraint ("the account's own recent posts"), and names the sibling tool that handles the other case (scrape_post). An agent can distinguish this from scrape_post and list_user_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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ("engagement on the account's own posts"), an explicit when-not-to-use / alternative ("for someone else's post use scrape_post"), and a downstream use case ("comment URNs for reply_comment"). Nothing is left to inference.

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?