Skip to main content
Glama

update_scheduled_post

Idempotent

Edit a not-yet-published post — caption, hashtags, schedule time, draft<->scheduled status, reel settings, automation link, or first comment.

Every parameter here is "leave alone unless set" — omit anything you don't want to change. caption="" and hashtags=[] are real values (clear it to blank/empty), not "unset"; there's no way through this tool to explicitly clear automation_id or first_comment back to none (only to a new value or leaving them alone) — cancel_scheduled_post and re-schedule if that's what you need.

share_to_feed/allow_comments/allow_remixing edit individual fields on the post's reel settings — passing one merges it onto the post's current reel settings rather than replacing the whole thing, so setting only share_to_feed doesn't reset allow_comments/allow_remixing back to their defaults.

status only accepts "draft" or "scheduled" — publishing/published/failed are written by the publish pipeline, not settable here. Moving draft -> scheduled charges the same reel-schedule quota schedule_reel does; a published or actively-publishing post can't be moved at all. Setting scheduled_at on an already-scheduled post moves it to that new time — the way to reschedule a story, which takes no caption or hashtags.

trial_reel turns a scheduled reel into a trial reel (non-followers first) or back into an ordinary one; trial_graduation ("MANUAL" or "SS_PERFORMANCE") changes how a trial is shared to followers. See schedule_reel. Turning a scheduled reel into a trial uses the plan's trial-reel allowance. Reels only.

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_id": "<workspace_id>",
      "post_id": "<post_id>"
    },
    "name": "update_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
captionNo
post_idYes
hashtagsNo
trial_reelNo
scheduled_atNo
workspace_idYes
automation_idNo
first_commentNo
share_to_feedNo
allow_commentsNo
allow_remixingNo
trial_graduationNo

Output Schema

NameRequiredDescriptionDefault
idYes
modeYes
statusYes
captionYes
is_trialNo
ig_media_idNo
scheduled_atNo
ig_account_idYes
publish_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations, which only say non-read-only, idempotent, non-destructive. It discloses the 'omit unless set' contract, that empty string and empty array are real values, merge-not-replace behavior for share_to_feed/allow_comments/allow_remixing, the quota cost of draft->scheduled, the trial-reel allowance consumption, and which state transitions are blocked. That is exactly the kind of hidden side-effect and cost information annotations cannot carry.

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 purpose and then organized into short thematic paragraphs, so the density is functional rather than padded. It is on the long side and a few clauses (the reel-settings merge example, the trial-reel sentences) restate related points, but almost every sentence carries a distinct behavioral fact.

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 13-parameter mutation tool with an output schema (so return values need no explanation), the description covers the transition rules, cost implications, merge semantics, and un-settable cases that an agent needs to call it correctly. Nothing material appears missing.

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

Parameters5/5

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

Schema description coverage is 0% with 13 parameters, so the description carries the full burden and does: it defines status's accepted values and why publishing/published/failed are rejected, explains scheduled_at as a move operation, documents trial_reel and trial_graduation's enum values, and calls out the un-clearable parameters. Only the two obvious identifiers, workspace_id and post_id, are left implicit.

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?

Opens with a specific verb and resource ('Edit a not-yet-published post') and then enumerates the exact editable surface: caption, hashtags, schedule time, draft<->scheduled status, reel settings, automation link, first comment. It also states a scope limit ('Reels only'), which lets an agent rule it out for non-reel posts without opening the 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?

Gives explicit routing conditions: use cancel_scheduled_post and re-schedule when you need to clear automation_id or first_comment to none, and points to schedule_reel for trial-reel semantics. It also states the exclusions an agent would otherwise guess wrong about — a published or actively-publishing post can't be moved — and clarifies that scheduled_at on an already-scheduled post is the way to reschedule a story.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources