FeedSquad

Reschedule Post

reschedule_post

DestructiveIdempotent

Moves a post to a new time. A scheduled post stays scheduled and publishes at the new time with no further approval; a draft stays a draft, and a ready post becomes a draft, with the new proposed time. Returns warnings if the new slot creates a posting cluster (3+ posts within an hour) on the same platform. Published posts cannot be rescheduled. Every response carries status_before, status_after and approval_required.

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

Input Schema

Name	Required	Description
`dry_run`	No	When true, the call validates and returns the conflict report without writing.
`post_id`	Yes	The post id to reschedule
`new_scheduled_date`	Yes	New publish time, ISO 8601. With an offset or Z it is used exactly as sent; without one (e.g. 2026-10-22T08:45) it is read in the founder's timezone (the timezone field of scheduling responses) and the response's time_input says so. The time is kept exactly as given, to the minute.

Output Schema

Name	Required	Description	Default
`to`	Yes
`from`	No
`kind`	Yes
`dry_run`	No
`post_id`	Yes
`platform`	Yes
`timezone`	No
`to_local`	No
`warnings`	No
`from_local`	No
`server_now`	No
`time_input`	No
`status_after`	No
`dashboard_url`	No
`status_before`	No
`approval_reset`	No
`scheduled_local`	No
`timezone_source`	No
`approval_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds behavior the annotations cannot express: scheduled posts publish at the new time with no further approval, ready posts silently downgrade to drafts, and a cluster warning fires at 3+ posts within an hour on the same platform. It also names the response envelope (status_before, status_after, approval_required), which is exactly the side-effect disclosure a destructive mutation needs.

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-loads the core action in the first sentence, then layers status transitions, warnings, and exclusions in a tight sequence. No sentence is filler, and each clause carries a distinct operational 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 destructive, idempotent mutation with an output schema present, the description covers the mutation's consequences per source status, the failure case, and the warning condition. Nothing an agent needs in order to call it safely is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already explains dry_run, post_id, and the ISO 8601 timezone-fallback rule in detail. The description adds no parameter-level meaning beyond that, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: "Moves a post to a new time." An agent can immediately tell this is a temporal mutation of an existing post. It stops short of the top mark because it never distinguishes itself from close siblings such as update_post, publish_post, or find_next_slot.

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

Usage Guidelines3/5

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

Gives one useful exclusion, "Published posts cannot be rescheduled," and implicitly defines the eligible population (scheduled, draft, ready posts) through the status-transition rules. It offers no routing guidance toward alternatives, so an agent choosing between reschedule_post and update_post gets no help.

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

All FeedSquad 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?