Skip to main content
Glama
EgiStr

linkedin-mcp

by EgiStr

Delete a LinkedIn Post

linkedin_delete_post
Destructive

Delete a LinkedIn post permanently using its post ID or URN. Removes the post from LinkedIn immediately with no undo.

Instructions

Permanently delete a LinkedIn post by its ID or URN.

⚠️ DESTRUCTIVE — This action cannot be undone.

Args:

  • post_id (string, required): Post ID or URN (e.g., 'post-123' or 'urn:li:share:post-123')

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns (JSON format): { "postId": string, // The ID that was deleted "status": "DELETED", // Always "DELETED" "note": string // Warning about permanence }

Requires scope: w_member_social

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesThe ID or URN of the post to delete (e.g., 'post-123' or 'urn:li:share:post-123')
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds critical context: the deletion is permanent and cannot be undone, and it requires the w_member_social OAuth scope. This gives the agent meaningful behavioral information beyond what annotations already declare.

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 well-structured and dense with useful information: a clear opening warning, parameter list, return format, and required scope. Every section earns its place, and the destructive warning is front-loaded for immediate visibility.

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 simple two-parameter destructive operation, the description is complete. It covers inputs, output shape, required scope, and permanence, and since there is no output schema, the explicit return example fills that gap.

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 100%, so the schema already documents both parameters. The description mostly repeats the schema details, providing the same examples for post_id and the same default for response_format, adding little new semantic value.

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 opens with a specific verb and resource: 'Permanently delete a LinkedIn post by its ID or URN.' This clearly distinguishes the tool from sibling tools like linkedin_create_post and linkedin_list_posts, so an agent can select it without ambiguity.

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 clearly states the operation and prerequisites, but it does not explicitly say when to prefer this tool over alternatives or mention when not to use it. The destructive warning implies careful usage, but there is no routing to sibling tools such as listing posts first to get a valid post_id.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EgiStr/linkedin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server