PostNitro

Delete Scheduled Post

postnitro_delete_scheduled_post

DestructiveIdempotent

Delete a scheduled post (or draft) and all of its related content. This action cannot be undone.

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": {
      "scheduledPostId": "<scheduledPostId>"
    },
    "name": "postnitro_delete_scheduled_post"
  }
}

Input Schema

Name	Required	Description	Default
`scheduledPostId`	Yes	The scheduled-post ID to delete (get from postnitro_list_scheduled_posts)

Output Schema

Name	Required	Description	Default
`message`	Yes	Confirmation message
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Explicitly warns that the action cannot be undone, reinforcing the destructiveHint annotation. Also mentions deletion of related content, providing side-effect detail.

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 sentences, concise and front-loaded with the primary action.

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?

Adequate for a simple delete operation; no extra context needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter scheduledPostId is well-described in the schema with a source reference. The tool description does not add extra meaning but is consistent.

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?

Clearly states the action (delete) and the target (scheduled post or draft) and scope (related content). Distinguishes from other scheduled post tools by its destructive nature.

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?

Does not explicitly compare to alternatives like update_scheduled_post, but the destructive intent is clear. Lacks guidance on when to use vs other tools, so a moderate score.

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

All PostNitro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?