PostRite

Retry a failed post

retry_post

Destructive

Retry publishing a FAILED or PARTIALLY_PUBLISHED post to the platforms that did not succeed. Runs now and replaces any automatic retry the post had scheduled. Refused with a 409 (code PUBLISH_RUN_IN_PROGRESS) while a publish run for the post is still going: wait for it to finish, then retry if the post is still not published. Refused with a 409 (code PUBLISH_RUN_CHECK_FAILED) when the queue could not be checked: nothing was changed, try again.

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

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post ID (from list_posts)
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description	Default
`post`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing that the call executes immediately and replaces any scheduled automatic retry, and by enumerating two distinct 409 conditions with their codes and whether state changed. That replacement side effect and the 'nothing was changed' guarantee are exactly the operational context an agent needs.

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?

Purpose and eligibility are front-loaded in the first sentence, followed by the side effect and then error handling in order of likely encounter. It is dense but nearly every clause carries actionable information; the error-code parentheticals are the only mildly verbose element.

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 an output schema present and only two fully documented parameters, the description covers everything else an agent needs: eligibility, immediate execution semantics, cancellation of scheduled retries, and both failure modes with recovery advice.

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 coverage is 100%, so postId and organizationId are already fully documented, including the multi-org conditionality. The description adds no syntax or format detail beyond referring to 'the post', so the baseline 3 applies.

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 (retry publishing) and resource (a post), plus the exact preconditions (FAILED or PARTIALLY_PUBLISHED) and scope (only the platforms that did not succeed). This clearly separates it from siblings like reschedule_post, cancel_post, and update_post.

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 explicit use conditions (only failed or partially published posts) and two concrete recovery paths for the 409 cases, including 'wait for it to finish, then retry if the post is still not published'. It stops short of naming alternatives such as reschedule_post or cancel_post for posts in other states, so the when-not guidance is implied rather than enumerated.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?