Mark

Reschedule Post

reschedule_post

Moves a post to a new future time. A draft keeps its status; any other post goes back to review at the new time and publishes only once approved again. Pass scheduledAt for any time, or slotId and date (both, from get_calendar's open slots) to fill one posting slot occurrence: a slot is a day and a number of posts, so Mark puts the post in that day's next free position, the channel's posting time plus 3 hours per post already there, or the next minute once that has passed today, in the workspace timezone. It refuses a slot on another channel, a day before today, or a full day, so two callers can't overfill it. The same status rules apply either way. Related: get_post, get_calendar, search_posts.

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

Input Schema

Name	Required	Description
`date`	No	The slot occurrence's local date (YYYY-MM-DD, workspace timezone), on the slot's weekday. Pass with slotId.
`postId`	Yes	Post id.
`slotId`	No	Posting slot id from get_calendar. Pass with date, instead of scheduledAt.
`scheduledAt`	No	New publish time as a UTC ISO string, in the future. Omit when you pass slotId and date.

Output Schema

Name	Required	Description	Default
`rev`	Yes
`appUrl`	Yes
`postId`	Yes
`status`	Yes
`scheduledAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 19, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "The slot occurrence's local date (YYYY-MM-DD, workspace timezone), on the slot's weekday. Pass with slotId.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / scheduledAt / description

Previous value: -"New publish time as a UTC ISO string, in the future."New value: +"New publish time as a UTC ISO string, in the future. Omit when you pass slotId and date."

addedInput schema / properties / slotId

Added value: +{
+  "description": "Posting slot id from get_calendar. Pass with date, instead of scheduledAt.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "postId",
-  "scheduledAt"
-]New value: +[
+  "postId"
+]

addedOutput schema / properties / scheduledAt
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "appUrl",
-  "postId",
-  "rev",
-  "status"
-]New value: +[
+  "appUrl",
+  "postId",
+  "rev",
+  "scheduledAt",
+  "status"
+]

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds detailed behavior beyond the annotations: drafts retain status, non-drafts revert to review and must be reapproved, and slot-based moves refuse cross-channel, past-day, or full-day slots. These are exactly the side effects and guardrails an agent needs before invoking a mutation.

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?

The purpose is front-loaded in the first sentence, followed by status rules, parameter modes, slot mechanics, and refusals. Despite its detail, every sentence carries operational value and there is no filler.

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 non-idempotent mutation with an output schema and full parameter coverage, the description covers the critical gaps: side effects on post status, approval workflow, slot assignment behavior, timezone handling, and refusal conditions. Nothing essential 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 baseline is 3. The description adds meaningful semantics by explaining that slotId and date must be used together and come from get_calendar's open slots, and by describing how Mark assigns the next free position within a slot day.

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?

The description states a specific verb and resource: 'Moves a post to a new future time.' It immediately distinguishes the draft vs. non-draft status behavior, making the tool's scope clearly distinct from siblings like edit_published_post or update_posting_slots.

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?

It clearly explains the two invocation modes: pass scheduledAt directly, or pass slotId and date together to fill a calendar slot. It also lists refusal conditions. However, it does not explicitly contrast this tool with nearby alternatives such as edit_published_post, so it falls short of full when-not/alternatives guidance.

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

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