Skip to main content
Glama

Reschedule a queued post

clipember_reschedule_post
Idempotent

Move a queued or draft post (clip or own video) to a new time. Fails if it already posted, failed or is unconfirmed — use clipember_retry_failed_post for those.

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

Input Schema

NameRequiredDescriptionDefault
postIdYes
scheduledForYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds value the annotations cannot: it defines the eligible state set (queued or draft, clip or own video) and documents the specific failure conditions that produce an error. It stops short of saying whether the change is reversible or what happens to approval state on a rescheduled post.

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?

Two sentences, zero filler. The capability and the eligible post types are front-loaded, and the exclusion plus pointer to the alternative follow immediately, so an agent can stop reading once it knows the post state.

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

Completeness3/5

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

For a two-parameter mutation with a rich annotation set and no output schema, the description covers eligibility, failure modes and the sibling route, which is most of what is needed. The remaining gap is the timestamp contract for scheduledFor — format and timezone — which is the single highest-risk detail and is absent from both the schema and the description.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description carries the full burden of explaining postId and scheduledFor. It only implies scheduledFor means 'new time'; it never states the required format, that the schema pattern enforces a UTC 'Z' timestamp, or how timezone conversion is handled — the most likely source of a malformed call. postId semantics (where the caller obtains it) are also unaddressed.

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 a queued or draft post ... to a new time') and scopes which post types are eligible (clip or own video). The name of the failing alternative, clipember_retry_failed_post, lets an agent separate this from a closely related sibling 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 Guidelines4/5

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

Gives an explicit when-not clause (already posted, failed, unconfirmed) and routes those cases to a named alternative tool, which is exactly the guidance an agent needs to avoid a guaranteed failure. It does not address the reschedule-vs-cancel distinction, so a user asking to stop a post still requires inference, but the primary routing decision is covered.

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