LinkedIn MCP Server

by oliverhruby

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_post

Fetch a LinkedIn post using its unique URN, returning the post's content and metadata for review or analysis.

Instructions

Get a post by URN.

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": {
      "post_urn": "<post_urn>"
    },
    "name": "get_post"
  }
}

Input Schema

Name	Required	Description	Default
`post_urn`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Get', hinting at a read operation, but does not state side-effect-free behavior, authentication needs, error behavior, or response characteristics.

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?

'Get a post by URN.' is a single, front-loaded sentence with no wasted words. For a one-parameter read tool, this is appropriately concise.

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?

The tool is simple and has an output schema, so the description does not need to explain return values. However, with no annotations and no usage guidance, the description lacks enough behavioral and selection context to be fully complete.

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. 'by URN' tells the agent that post_urn is the identifier used to select the post, adding some meaning beyond the raw schema, but it does not provide format details, examples, or where the URN comes from.

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?

The description clearly states the verb ('Get'), resource ('post'), and selection mechanism ('by URN'). It distinguishes itself from siblings like create_post, delete_post, and list_comments by signaling a single-item read operation.

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

Usage Guidelines2/5

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

The description gives no guidance on when to prefer this tool over alternatives such as linkedin_get or when not to use it. It implies the obvious context — retrieving a post by URN — but offers no exclusions or comparisons.

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