Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Reschedule

post_reschedule

Move a social media post to a new scheduled time while preserving its text, channels, and media; draft status stays, and approval-required posts wait for manager review.

Instructions

Move a social media post to another time. Text, channels and media stay; a draft stays a draft with the new planned time. When the organization requires approval, a member's post waits for a manager (status PENDING_APPROVAL).

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

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post id (see post_list).
timezoneNoIANA time zone the post is planned in, e.g. Europe/Vienna. Shown in the calendar.
scheduledAtYesWhen to publish: ISO 8601 date-time with UTC offset, e.g. 2026-11-10T10:00:00+01:00. At least 10 minutes from now.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (which only say it is a non-destructive, non-idempotent write), the description discloses that text, channels and media are untouched, that a draft remains a draft, and that approval-gated organizations put a member's post into PENDING_APPROVAL. That is substantive state-transition information an agent could not derive from the schema or hints.

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 short sentences, front-loaded with the action, followed by the invariants and the approval edge case. Every sentence carries distinct information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with full schema coverage and no output schema, the description covers the effect, the preserved fields, and the approval-state consequence. It stops short of saying what the call returns or how failures behave, but nothing essential for correct invocation 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%, with each parameter already documented including the ISO 8601 offset format, the 10-minute minimum, and the timezone guidance. The description adds no parameter-level meaning beyond this, so the baseline of 3 applies.

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 ('Move a social media post to another time') and clarifies that content, channels and media are preserved while only the planned time changes. It is clearly distinguishable from post_create or post_schedule by the word 'move', although it never names a sibling explicitly.

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?

Usage is implied: this is the tool for changing the publish time of a post that already exists, including drafts. There is no explicit statement about when not to use it or which sibling to pick for creating or initially scheduling a post, leaving that routing to the agent's inference.

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

Deploy Server

Other Tools