Skip to main content
Glama

Retry a failed or unconfirmed post

clipember_retry_failed_post
Idempotent

Requeue a failed or unconfirmed post to publish again right now. UNCONFIRMED means the platform timed out after the video was already sent, so it may be live: before retrying, ask the user to check their profile on that platform — if the post is there, do NOT retry (cancel it instead), or it will be published twice.

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": "clipember_retry_failed_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this is a non-readonly, open-world, non-destructive, idempotent mutation, and the description adds behavior those hints cannot express: what UNCONFIRMED actually means (platform timed out after the video was sent), that the post may already be live, and the concrete consequence of retrying (double publication). That is high-value disclosure well beyond the structured fields; the 'published twice' warning and idempotentHint=true refer to different things (platform duplication vs. repeated calls) so they are not in conflict.

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, front-loaded with the action, then the risk condition. The UNCONFIRMED explanation is dense but every clause prevents a specific misuse, and the em-dash structure makes the branch (check profile → then retry or cancel) easy to follow.

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 one-parameter mutation with full annotation coverage and no output schema, the description covers the risk profile, the state semantics, and the pre-call check. The only meaningful omission is how an agent locates or validates the postId and what a successful requeue returns or costs.

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?

There is one required parameter with 0% schema description coverage, and the description never explains postId's format, where to obtain it, or how to determine a post's failed/unconfirmed state. It does implicitly constrain which ids are valid (a post currently in failed or unconfirmed status), which is real semantic value, but the parameter itself remains undocumented.

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?

The description states a specific verb and resource ('Requeue a failed or unconfirmed post') plus a timing qualifier ('publish again right now') that implicitly separates it from reschedule/repeat style operations. It does not name a sibling tool, so an agent must infer the contrast, but the action and the target state are unambiguous.

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?

It gives an explicit entry condition (the post is failed or unconfirmed) and an explicit when-NOT-to case with the alternative action spelled out: if the post is already live on the platform, do not retry, cancel instead. It also injects a required user-verification step before invocation, which is exactly the guidance an agent needs to avoid a wrong call.

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