Skip to main content
Glama

Move a planned post or mark it ready

reschedule_social_post
DestructiveIdempotent

Move an existing planned post to another day, or mark it draft or ready (and, for a post going to YouTube, change its yt_title / yt_description — update_social_post edits those too). Takes the post id from get_calendar. Marking a post ready does NOT publish it (queue_post_for_publishing does); a post that is already queued keeps its accounts and goes out on the new day. post.status in the reply is only the calendar's draft/ready mark — publishing says whether and when the post will actually go out. Free. To add a new post use schedule_social_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": {
      "brand_id": "<brand_id>",
      "post_id": "<post_id>"
    },
    "name": "reschedule_social_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo
post_idYesThe post id from get_calendar
brand_idYesBrand workspace id from list_brands
yt_titleNoThe YouTube title. Same as update_social_post `yt_title`.
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
scheduled_dateNoThe new day, YYYY-MM-DD: today or later in the brand's time zone. A day already gone is refused.
yt_descriptionNoThe YouTube description. Same as update_social_post `yt_description`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / yt_description
      Added value: +{
      +  "description": "The YouTube description. Same as update_social_post `yt_description`.",
      +  "maxLength": 5000,
      +  "type": "string"
      +}
    • addedInput schema / properties / yt_title
      Added value: +{
      +  "description": "The YouTube title. Same as update_social_post `yt_title`.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / yt_description
      Removed value: -{
      -  "description": "The YouTube description. Empty string clears it.",
      -  "maxLength": 5000,
      -  "type": "string"
      -}
    • removedInput schema / properties / yt_title
      Removed value: -{
      -  "description": "The YouTube title, used when the post goes to a YouTube account. Empty string clears it.",
      -  "maxLength": 100,
      -  "type": "string"
      -}
  4. Changed2 schema fields changed
    • addedInput schema / properties / yt_description
      Added value: +{
      +  "description": "The YouTube description. Empty string clears it.",
      +  "maxLength": 5000,
      +  "type": "string"
      +}
    • addedInput schema / properties / yt_title
      Added value: +{
      +  "description": "The YouTube title, used when the post goes to a YouTube account. Empty string clears it.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that marking ready does not publish, that an already-queued post keeps its accounts and moves to the new day, and that `post.status` differs from `publishing` in the reply. It also notes cost ('Free') and that past dates are refused (though the latter is largely echoed in the schema). The destructive aspect of overwriting the prior date is implied but not spelled out.

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?

Front-loaded with the core action, then the caveats and sibling routing; nearly every clause carries information. It is dense with em-dash parentheticals, which slightly slows scanning but wastes no 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?

With no output schema, the description supplies the key return-value semantics (`post.status` vs `publishing`), covers the publishing side effect, and names the source of the post id. Nothing material is missing for correct invocation.

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 86%, so the baseline is 3; the description adds real value by clarifying that `status` is a calendar-only draft/ready mark distinct from actual publishing, and that `yt_title`/`yt_description` duplicate update_social_post's fields. The `scheduled_date` time-zone/refusal semantics come from the schema rather than the prose.

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 the specific verb+resource ('Move an existing planned post to another day, or mark it draft or ready') and carves out its exact scope, including the YouTube field side-effect. An agent can tell it apart from schedule_social_post, update_social_post and queue_post_for_publishing from the description alone.

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 routes to alternatives with conditions: 'To add a new post use schedule_social_post', publishing is queue_post_for_publishing, and yt field edits are also covered by update_social_post. It also states the entry point for the id (get_calendar).

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