Linked API MCP

fetch_post

Retrieve LinkedIn post data including comments and reactions. Provide a post URL to get its content, and optionally fetch comments and reactions with configurable limits and sorting.

Instructions

Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action).

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": {
      "postUrl": "<postUrl>"
    },
    "name": "fetch_post"
  }
}

Input Schema

Name	Required	Description
`postUrl`	Yes	LinkedIn URL of the post. (e.g., 'https://www.linkedin.com/posts/username_activity-id')
`retrieveComments`	No	Optional. When true, also retrieve comments for the post. Configure via commentsRetrievalConfig.
`retrieveReactions`	No	Optional. When true, also retrieve reactions for the post. Configure via reactionsRetrievalConfig.
`commentsRetrievalConfig`	No	Optional. Applies only when retrieveComments is true. Controls comments retrieval (limit, replies, sort).
`reactionsRetrievalConfig`	No	Optional. Applies only when retrieveReactions is true. Controls reactions retrieval (limit).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / properties / commentsRetrievalConfig

Added value: +{
+  "description": "Optional. Applies only when retrieveComments is true. Controls comments retrieval (limit, replies, sort).",
+  "properties": {
+    "limit": {
+      "description": "Optional. Max number of comments to retrieve. Defaults to 10, with a maximum value of 500.",
+      "type": "number"
+    },
+    "replies": {
+      "description": "Optional. When true, include replies to comments (threaded).",
+      "type": "boolean"
+    },
+    "sort": {
+      "description": "Optional. Sort order for comments. One of 'mostRelevant' or 'mostRecent'.",
+      "enum": [
+        "mostRelevant",
+        "mostRecent"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / reactionsRetrievalConfig

Added value: +{
+  "description": "Optional. Applies only when retrieveReactions is true. Controls reactions retrieval (limit).",
+  "properties": {
+    "limit": {
+      "description": "Optional. Max number of reactions to retrieve. Defaults to 10, with a maximum value of 1000.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / retrieveComments

Added value: +{
+  "description": "Optional. When true, also retrieve comments for the post. Configure via commentsRetrievalConfig.",
+  "type": "boolean"
+}

addedInput schema / properties / retrieveReactions

Added value: +{
+  "description": "Optional. When true, also retrieve reactions for the post. Configure via reactionsRetrievalConfig.",
+  "type": "boolean"
+}

First observedAug 23, 2025

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It states 'retrieve its data', implying a read operation, but does not disclose potential rate limits, authentication requirements, or any side effects beyond the action name.

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?

The description is a single, concise sentence that includes the key action and optional capabilities. No extraneous information.

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?

Given no output schema and moderate complexity (5 params, nested objects), the description is adequate but could mention return format or pagination. However, the schema covers parameters well.

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?

All parameters are fully described in the schema (100% coverage), so the description adds minimal extra meaning beyond mentioning the action and optional comments/reactions. Baseline score 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?

The description clearly specifies the verb 'Open and retrieve' and the resource 'LinkedIn post data', including optional comments and reactions. It is distinct from siblings like comment_on_post or create_post.

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

Usage Guidelines4/5

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

The description implies this tool is for retrieving post data, but does not explicitly state when to use it versus alternatives or any exclusions. However, the context is clear enough for an agent.

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