Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cancel_post

Cancel a scheduled or approved post and revert it to draft status without deletion. For permanent removal, use delete_post.

Instructions

Cancel a scheduled or approved post, reverting it to draft status without deleting it. Use delete_post to remove it entirely.

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

Input Schema

NameRequiredDescriptionDefault
postIdYesPost ID to cancel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the non-destructive state change. However, it omits any details about permissions, idempotency, or response behavior, keeping it moderately transparent.

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?

Two concise sentences deliver the action, scope, outcome, and alternative in a front-loaded manner with zero waste.

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?

The tool is simple with one documented parameter and no output schema. The description adequately covers what, when, and why, though a note on return value or side effects would make it 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?

The sole parameter postId is fully documented in the schema, so the description adds no extra meaning. Baseline 3 is appropriate since the schema does all the heavy lifting and no additional semantics are needed.

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 uses a specific verb 'cancel' targeting 'scheduled or approved post' and explains the outcome ('reverting it to draft status'), clearly distinguishing it from sibling delete_post.

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

Usage Guidelines5/5

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

It explicitly states when to use (scheduled or approved posts) and provides an alternative: 'Use delete_post to remove it entirely.' This gives clear context and an exclusion.

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