Skip to main content
Glama

Postemi: Social Media Scheduler

reschedule_post

Idempotent

Move one or more scheduled or draft posts to a new publish time without changing their content. A draft stays a draft. Call get_workspace_context first if the user gave a local time. Failed posts are not moved here: use retry_post. Published posts cannot be moved.

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

Input Schema

NameRequiredDescriptionDefault
dateYesThe new publish time, ISO 8601 UTC.
postIdsYespostIds from list_posts. Each is one channel; give every channel the user means.

Output Schema

NameRequiredDescriptionDefault
errorsNo
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=true, and openWorldHint=true, but the description adds real behavioral context beyond them: content is preserved, drafts remain drafts, published posts are rejected, and failed posts belong to retry_post. The one meaningful gap is batch semantics — with up to 20 channel postIds, it never says whether a partial failure moves some channels and errors others, which matters for a multi-target 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?

Four short sentences, front-loaded with the core action and constraint, then the prerequisite and the two exclusions. Every sentence carries a distinct, actionable fact; there is no restatement of the tool name or 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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. What remains under-specified is batch behavior for multi-channel postIds and whether past-dated times are rejected — minor but real omissions for an openWorld mutation.

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% and the schema already explains ISO 8601 UTC, the 20-item cap, and the one-channel-per-ID rule, so the baseline would be 3. The description adds genuine meaning by telling the agent to resolve local times via get_workspace_context before calling, which is a parameter-preparation step the schema does not convey.

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 a specific verb and resource ('Move one or more scheduled or draft posts to a new publish time') plus the key invariant ('without changing their content'). It also explicitly carves out the sibling boundary with retry_post and excludes published posts, so an agent can distinguish it from update_post or retry_post without opening any schema.

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?

Gives explicit when-to-use preconditions ('Call get_workspace_context first if the user gave a local time') and explicit when-not cases with the correct alternative ('Failed posts are not moved here: use retry_post', 'Published posts cannot be moved'). Both exclusion and routing are spelled out rather than inferred.

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.