Skip to main content
Glama
Sign In
linkedin-mcp-server

linkedin-mcp-server

by isucorp-taimiralain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_delete_post

Delete a LinkedIn post by its ID to remove outdated, unwanted, or incorrect content from your profile.

Instructions

Delete a LinkedIn post by its ID.

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": {
      "postId": "<postId>"
    },
    "name": "linkedin_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe ID of the post to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavioral traits. It only states the action 'delete' without explaining whether the deletion is permanent, whether it requires specific permissions, whether the post must belong to the authenticated user, or what errors may occur.

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, clear sentence with no unnecessary words. It conveys the essential purpose efficiently.

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 with one parameter, but the description lacks important context for a destructive operation, such as whether deletion is reversible, required permissions, or behavior when the post does not exist. While the core action is clear, the absence of any safety or precondition information leaves it incomplete.

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?

The input schema already fully describes the single parameter (postId) with a clear description. The tool description adds no extra semantic meaning beyond restating 'by its ID,' so the baseline score of 3 is appropriate given 100% schema coverage.

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 identifies the action ('Delete') and the resource ('a LinkedIn post by its ID'). This is distinct from sibling tools like linkedin_get_posts and linkedin_create_post, which perform different actions.

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 description states the action but gives no explicit guidance on when to use it versus alternatives. It is implied that this tool is for deleting posts, but no context about prerequisites, ownership, or when not to use it is provided.

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

Deploy Server

Other Tools