Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_post

Cancel and delete posts in any status—draft, scheduled, or posted—to remove unwanted content from your queue and social media.

Instructions

Cancel and delete a post regardless of its current status (draft, scheduled, or posted).

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": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesPost ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It communicates the destructive action ('delete') and scope (all statuses), but does not disclose irreversibility, side effects on linked resources, or permission requirements. This is a meaningful gap for a deletion tool.

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 front-loads the action and resource, then adds scope. Every word adds value with no redundancy or filler.

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?

For a simple one-parameter delete operation, the description covers purpose and scope. However, it omits a warning about permanence or a distinction from cancel_post. Given the tool's simplicity, this is adequate but has clear room for improvement.

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 coverage is 100% (postId described as 'Post ID to delete'). The description adds no parameter-specific detail, but the schema already sufficiently documents the single parameter, so the baseline score of 3 is appropriate.

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 states a clear verb ('Cancel and delete') and resource ('a post'), and adds valuable scope distinction by specifying 'regardless of its current status (draft, scheduled, or posted)'. This distinguishes it from sibling tools like cancel_post, which likely only handles scheduled posts.

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 implies when to use it (for any post status) but does not explicitly name alternatives or provide exclusions. Since a sibling cancel_post exists, direct comparison would strengthen guidance, but the 'regardless of status' phrase offers reasonable context.

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