Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Delete scheduled post

delete_scheduled_post
DestructiveIdempotent

Permanently delete a draft or scheduled post from Blaze, including its per-platform targets. It will not be published. This cannot be undone.

Published or in-progress posts are rejected: deleting them in Blaze would not remove them from the social platforms, so they must be deleted on each platform directly. To keep a post but stop it from publishing, use edit_scheduled_post with status "draft" instead.

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": {
      "workspace_key": "<workspace_key>",
      "id": "<id>"
    },
    "name": "delete_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric ID of the scheduled post to delete.
workspace_keyYesKey of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description still adds material detail: deletion is permanent and irreversible, cascades to per-platform targets, and the post will not be published. The rejection behavior for published/in-progress posts is a runtime trait no annotation conveys.

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?

Front-loaded with the action and its consequences, then the rejection rule, then the softer alternative — a logical escalation. Three short paragraphs with no filler; every sentence carries new decision-relevant information.

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?

Two required params fully documented, no output schema to explain, annotations covering safety and idempotency, and the description closes the remaining gaps: irreversibility, cascade scope, and the failure mode for published posts. Nothing an agent needs to call this correctly is missing.

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%, so both parameters (id, workspace_key) are already documented, including the list_workspaces hint. The description adds only the scope qualifier that the id refers to a draft or scheduled post; it gives no format or edge-case detail beyond the schema.

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?

States a specific verb ('Permanently delete') and resource ('a draft or scheduled post') plus the scope ('including its per-platform targets'). It also names the exclusions, which makes it trivially distinguishable from edit_scheduled_post, get_scheduled_post, and publish_post_now without opening a schema.

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?

Explicitly defines when not to use it: published or in-progress posts are rejected, with the reason given (Blaze deletion would not remove them from the platforms). It also names the alternative for the adjacent intent — edit_scheduled_post with status "draft" to halt publishing without deleting.

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

All Blaze toolsInspect
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