Skip to main content
Glama

Reschedule or edit a scheduled post

reschedule_post
DestructiveIdempotent

Moves a scheduled post that has not gone out yet to a new time, and can change its caption, title, per-network overrides or first comment at the same time. Only after the user agreed. The time is absolute, so the same call twice leaves the same post.

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": {
      "post_id": "<post_id>"
    },
    "name": "reschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
captionNo
post_idYes
timezoneNoIANA zone (default: the post's own)
overridesNoPer network (tiktok, instagram, youtube, facebook, linkedin, threads, reddit, bluesky): a different caption and, on titled networks (YouTube), a different title. Networks left out use caption / title.
scheduled_atNoNew local time YYYY-MM-DDTHH:mm in `timezone`
first_commentNoEmpty string removes it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/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 usefully explains why the latter holds ('the time is absolute, so the same call twice leaves the same post'), which prevents a relative-time misreading. But it never discloses what the destructive part actually destroys — whether omitted per-network overrides are cleared or preserved, or whether rescheduling invalidates existing approval — leaving the highest-risk behavior to the schema.

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?

Three tight sentences: capability first, precondition second, idempotency guarantee last — well front-loaded with no filler. The fragment 'Only after the user agreed' is slightly ambiguous about what was agreed to, but the economy is worth the trade-off.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter destructive mutation with a nested overrides object and no output schema, the definition covers the capability and the confirmation gate but omits the highest-value unknowns: what happens to fields/overrides not supplied, and whether a moved post must be re-approved. Adequate to select the tool, thin on the consequences of calling it.

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 only 57%, so the description must compensate, and it does: it names every editable field (time, caption, title, overrides, first comment) and clarifies that the time is absolute, which pairs with the schema's 'new local time in `timezone`'. It adds no detail on post_id or timezone defaults, but those are already documented in 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 and resource ('moves a scheduled post ... to a new time') and enumerates the editable payload ('caption, title, per-network overrides or first comment'). The qualifier 'that has not gone out yet' cleanly bounds the operation against publish_post and cancel_post without needing to name them.

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

Usage Guidelines4/5

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

Gives a real precondition, 'Only after the user agreed,' which is the key gating rule for a destructive mutation and stops an agent from acting unilaterally. It does not, however, point at alternatives (e.g., cancel_post when the user wants to drop rather than move the post), so it stops short of a full when/when-not treatment.

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.