Skip to main content
Glama

Reschedule post

reschedule_post

Move a scheduled post (any network) to a new publish time, on every network target that is not yet published. Only posts with status scheduled can be moved: a paused post answers 409 POST_NOT_RESCHEDULABLE (use resume_post with scheduledAt instead), a draft or published one too. The time must respect the minimum lead (400 SCHEDULED_TOO_SOON). Approval is NOT changed or bypassed: an approved post stays approved, an unapproved one still needs a human. Requires scope POSTS_WRITE.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe scheduled post id.
scheduledAtYesNew publish time, ISO 8601 WITH time zone, e.g. 2026-10-01T09:00:00Z or +02:00. Must be at least 10 minutes from now, otherwise SCHEDULED_TOO_SOON (not retryable; the error names the earliest allowed time).

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?

No annotations exist, so the description carries the full burden and does: it discloses the 409 POST_NOT_RESCHEDULABLE behavior and which statuses trigger it, the 400 SCHEDULED_TOO_SOON lead-time check, that approval state is neither changed nor bypassed, and the required POSTS_WRITE scope.

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 core action sentence, then failure modes, then approval semantics, then scope. Error codes are cited inline where they matter; no filler sentences.

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?

Complete for a 2-param mutation tool with no annotations and no output schema: preconditions, error codes, approval interaction, required scope, and the alternative tool are all present. An agent can call this correctly without further discovery.

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 baseline is 3; the description adds the 10-minute minimum lead and the 'ISO 8601' expectation, though scheduledAt's schema description already covers both formats and the error. Some reinforcement rather than new meaning.

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?

Specific verb + resource + scope: 'Move a scheduled post (any network) to a new publish time, on every network target that is not yet published.' This distinguishes it from update_post and resume_post by naming the exact operation and its all-targets semantics.

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 states the precondition (status must be scheduled) and routes the paused case to the alternative: 'use resume_post with scheduledAt instead'. Also names what happens for drafts and published posts, closing off misuse paths.

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