Reach MCP — LinkedIn for AI agents

cancel_job

DestructiveIdempotent

Cancel a job: its pending items will never run. Items already executed are unaffected. Cannot be undone. Irreversible for the pending items (executed ones stay); confirm with the user. To stop temporarily use pause_job.

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": {
      "job_id": "<job_id>"
    },
    "name": "cancel_job"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job id, as returned by create_job or list_jobs.
`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
`id`	No
`items`	No
`label`	No
`action`	No
`source`	No
`status`	No
`totals`	No
`window`	No
`resume_at`	No
`account_id`	No
`created_at`	No
`started_at`	No
`completed_at`	No
`next_item_at`	No
`pause_reason`	No	quota_reached \| account_disconnected \| billing \| manual

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally; the description adds the concrete consequences (pending items never run, executed items remain, cannot be undone). It does not restate the idempotency-key retry semantics, but those live in the schema description, so this is a modest gap rather than a miss.

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 the operation and its consequence, and every clause is decision-relevant. Minor redundancy between 'Cannot be undone' and 'Irreversible for the pending items' costs a point, but there is no filler.

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 destructive, irreversible tool with a full output schema and complete annotations, the description supplies the consequence model and the pause_job alternative an agent needs. What is missing — post-cancellation job state and response shape — is covered by the output schema.

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%, including job_id provenance ('as returned by create_job or list_jobs') and a full idempotency_key explanation, so the schema carries all parameter meaning. The description adds nothing about parameters, which is the correct baseline when coverage is complete.

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+resource ('Cancel a job') and immediately clarifies scope: pending items will never run, executed items are unaffected. It explicitly contrasts with the sibling pause_job, so an agent can distinguish it from create_job/list_jobs/get_job without opening schemas.

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 routes to the alternative: 'To stop temporarily use pause_job.' It also adds a when-to-use guardrail — 'confirm with the user' — for an irreversible action, which is exactly the decision context an agent needs.

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?