Reach MCP — LinkedIn for AI agents

delete_scheduled_post

DestructiveIdempotent

Delete a scheduled LinkedIn post. post_urn is the URN returned by list_scheduled_posts (e.g. urn:li:ugcPost:…). Only for posts still scheduled; irreversible, confirm with the user. A published post cannot be deleted through Reach.

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_urn": "<post_urn>"
    },
    "name": "delete_scheduled_post"
  }
}

Input Schema

Name	Required	Description
`post_urn`	Yes	URN of the scheduled post (urn:li:…), from list_scheduled_posts.
`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.

Output Schema

Name	Required	Description	Default
`deleted`	No
`post_urn`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the key operational context the annotations cannot: the action is irreversible and requires user confirmation, and the target scope is limited to still-scheduled posts. That is exactly the 'what gets destroyed / preconditions' context the rubric rewards.

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

Conciseness5/5

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

Three tightly packed sentences: identity first, then parameter provenance, then scope and safety constraints. No filler and every clause carries actionable information.

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?

For a destructive single-target delete with a full input schema, an output schema, and complete annotations, the description covers everything the agent needs: the target, its source, the exclusion of published posts, and the confirmation/irreversibility requirement.

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%, so post_urn, account_id and idempotency_key are already fully documented in the schema. The description restates post_urn's origin (list_scheduled_posts) and gives an example URN shape, which is mildly useful but largely duplicates the schema, 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?

States a specific verb (delete) and resource (scheduled LinkedIn post), and scopes it to scheduled rather than published posts, which distinguishes it from the sibling update_scheduled_post and list_scheduled_posts. An agent can tell exactly what this does without opening the 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 (posts still scheduled, URN sourced from list_scheduled_posts) and when-not (a published post cannot be deleted through Reach), plus a workflow prerequisite to confirm with the user. Nothing about routing to this tool versus its siblings 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 — 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?