Skip to main content
Glama
Sign In

Blaze

by ai.blaze.app
OverviewDiscussionsAdmin

Edit scheduled post

edit_scheduled_post
DestructiveIdempotent

Change an existing draft or scheduled post: its publish time (post_at), its caption, per-platform captions, or its status (draft or scheduled). Fields you omit are left as they are. Call get_scheduled_post first to see the post's targets and captions.

For a post with one platform, pass caption. For a post sent to several platforms, pass captions with one entry per platform to change; platforms you leave out keep their caption. If a post has two targets on the same platform, identify each by target_id (listed by get_scheduled_post) instead of provider.

Setting status to "scheduled" queues the post to publish at post_at to the connected social accounts. Published or in-progress posts cannot be edited and are rejected.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric ID of the scheduled post to edit.
statusNoMove the post between draft and scheduled.
captionNoNew caption for the post's primary content. For a single-target post this is the post's caption; for a multi-target post it's the fallback used by any platform without its own entry in captions.
post_atNoNew ISO 8601 publish datetime.
captionsNoPer-platform caption overrides, for posts with more than one target.
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.8/5.0
Behavior5/5

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

Despite annotations already flagging destructive/idempotent/open-world, the description adds non-obvious behavior: omitted fields are left untouched (partial-update semantics), missing platforms keep their caption, and status='scheduled' queues publishing to connected accounts. It also discloses the hard failure mode for published/in-progress posts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the editable fields, then the guidance blocks in logical order. It is slightly long and some sentences restate schema descriptions (e.g. target_id disambiguation), but no paragraph is wasted.

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 6-parameter mutation tool with no output schema, the description covers prerequisites, partial-update behavior, per-target semantics, and rejection conditions. An agent has enough to invoke it correctly; only return value is unspecified, which is minor for an edit operation.

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?

Schema coverage is 100%, so the schema already documents each parameter and the baseline is 3. The description still adds real value by explaining the conditional relationship between caption and captions and the provider-vs-target_id disambiguation rule, which the schema only states piecewise.

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 (change) and resource (existing draft or scheduled post) and enumerates exactly which fields are editable: post_at, caption, per-platform captions, status. This clearly separates it from schedule_posts (create) and get_scheduled_post (read) among the siblings.

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 tells the agent to call get_scheduled_post first for targets and captions, then gives branching guidance: single platform use caption, multi-platform use captions, same-platform duplicates use target_id instead of provider. It also defines the rejection case (published or in-progress posts).

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