linkedin-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Unsave a job on LinkedIn

linkedin_unsave_job

Remove a job from the saved list on LinkedIn using a user-confirmed actionId. Changes LinkedIn state only after explicit terminal confirmation.

Instructions

[EXECUTE - external action; REQUIRES the user to have confirmed this exact action] Removes a job from the saved list on LinkedIn (changes LinkedIn state). Requires an actionId from linkedin_prepare_save_job (mode "unsave") that the USER has confirmed in their own terminal.

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": {
      "actionId": "<actionId>"
    },
    "name": "linkedin_unsave_job"
  }
}

Input Schema

Name	Required	Description	Default
`actionId`	Yes	The actionId returned by the matching prepare tool, after the user confirmed it.

Output Schema

Name	Required	Description	Default
`data`	No
`action`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false; the description adds the crucial external-side-effect context ('changes LinkedIn state'), the terminal-confirmation requirement, and the execute-stage guard. This goes well beyond what the structured annotations convey.

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 execute marker and the core action, and stays to two sentences. Slight redundancy between 'REQUIRES the user to have confirmed this exact action' and 'that the USER has confirmed in their own terminal' costs it the top mark.

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 single-parameter execution tool with an output schema, everything an agent needs is present: the state-changing nature, the confirmation gate, and the source of the required actionId. No return-value explanation is needed since an output schema exists.

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%, so the actionId definition is already documented. The description adds provenance meaning (must come from the matching prepare tool, post-confirmation), which is useful but largely mirrors the schema text.

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: 'Removes a job from the saved list on LinkedIn'. This clearly distinguishes it from linkedin_save_job and linkedin_prepare_save_job, and the '[EXECUTE]' framing signals the execution stage versus the prepare stage.

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 names the prerequisite chain: the actionId must come from linkedin_prepare_save_job (mode "unsave") and must have been confirmed by the user in their own terminal. An agent knows both which sibling to call first and the gate condition for invoking this one.

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