PostRite

Reschedule a post

reschedule_post

Destructive

Move a scheduled post to a new time. Only works on SCHEDULED posts. WARNING: a new time that is in the past, or less than about 2 minutes from now, does not wait — the post is published immediately to every connected platform, and that cannot be undone. The scheduledAt must include the UTC offset (e.g. 2026-10-20T09:00:00-03:00); the timezone parameter is stored for display and does not shift it.

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

Input Schema

Name	Required	Description
`postId`	Yes	The post ID (from list_posts)
`timezone`	No	IANA timezone stored for display; does not shift scheduledAt
`scheduledAt`	Yes	New publish time: ISO 8601 date-time with the UTC offset included, e.g. 2026-10-20T09:00:00-03:00 or 2026-10-20T12:00:00Z. The timezone parameter is stored for display only and does not shift this time, so convert local times to an offset yourself. In the past or under ~2 minutes from now it publishes immediately
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description	Default
`post`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them by explaining the exact failure mode: a time in the past or under ~2 minutes away causes immediate publication to every connected platform and cannot be undone. That is precisely the operational risk an agent must know before calling.

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?

Three sentences, no filler, with the destructive warning front-loaded before the parameter mechanics. Every sentence carries either a constraint or a hazard the caller must act on.

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?

With full schema coverage, annotations, and an output schema, the description only needs to supply the behavioral hazard and the timezone pitfall — and it does both. Nothing an agent needs in order to call this safely is missing.

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 baseline is 3, but the description adds real interpretive value by stressing that scheduledAt must carry the UTC offset and that the timezone parameter is display-only and does not shift the time — a subtle trap the schema states but does not emphasize. postId and organizationId are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Move a scheduled post to a new time" gives a specific verb and resource, and "Only works on SCHEDULED posts" narrows the scope. It does not explicitly name update_post or cancel_post as the alternative for other editing needs, so sibling differentiation is implied rather than stated.

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?

The precondition (post must be in SCHEDULED state) and the danger zone (past times or under ~2 minutes) are stated clearly, which tells the agent when this call is safe. It stops short of naming alternatives such as update_post for content changes or cancel_post to stop a post entirely.

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

All PostRite tools Inspect

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

Need Help?