linkedin-mcp

Update the LinkedIn profile

linkedin_update_profile

Update a LinkedIn profile's headline, about section, or location and preview the changes with a diff before publishing.

Instructions

Update the headline, the about section or the location on the profile. This is a dry run unless publishing has been enabled on the server, so it reports what would change before it changes anything. Returns the diff against the live profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_update_profile"
  }
}

Input Schema

Name	Required	Description	Default
`about`	No
`headline`	No
`location`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the whole load and does well: it discloses that the call is a dry run unless publishing is enabled server-side, and that it returns a diff against the live profile. This is exactly the safety context an agent needs before mutating a profile; only the per-field failure/partial-update behavior is missing.

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 short sentences, front-loaded with the scope, then execution mode, then return value. Nothing repeats what the schema already says and no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema covers the return value and the dry-run note covers the main risk, but for a mutation tool with zero annotation coverage and all-optional string params defaulting to empty, the description leaves open whether omitted/empty fields mean 'no change' or 'clear the field'. That ambiguity matters for correct invocation.

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 0%, so the description must compensate. It names all three fields, mapping them one-to-one to the parameters, but adds no semantics beyond the names — no length limits, formatting rules, or whether an empty string clears a field, which is critical given every param defaults to "".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus the exact fields it touches (headline, about, location), which lets an agent distinguish it from linkedin_get_profile. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The dry-run/publishing note implies a preview-then-publish workflow, but the description never states when to choose this over linkedin_get_profile or linkedin_publish_post, nor what to do with the returned diff. Usage is inferable rather than stated.

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

Deploy Server