Skip to main content
Glama

retry_failed_post

Publish a post that failed again — right now (publish_now=true) or at a new time (scheduled_at, a future ISO-8601 time WITH a timezone offset). Exactly one of the two. Only a post whose status is "failed" can be retried.

Find the post with list_scheduled_posts(status=["failed"]); each failed row carries publish_error, the reason in plain words. Tell the user that reason first: when the cause is an expired Instagram connection or media Instagram rejected, retrying changes nothing until they fix it (reconnect in Settings → Connections, or upload different media). When the failure was transient, retry. If the post should not go out at all, use cancel_scheduled_post.

The post keeps its caption, media, cover and settings. This publishes to Instagram (immediately, or at the time given), so confirm with the user before calling it.

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>"
    },
    "name": "retry_failed_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
publish_nowNo
scheduled_atNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
modeYes
statusYes
captionYes
is_trialNo
ig_media_idNo
scheduled_atNo
ig_account_idYes
publish_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, destructive=false and non-idempotency; the description adds real value beyond that by noting the retry preserves caption, media, cover and settings, that it publishes to Instagram externally, and that the user should be confirmed with first. It doesn't cover what happens to the error state or whether retries are rate-limited, keeping it short of a 5.

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?

Front-loads the action and its two modes, then the eligibility rule, then the diagnostic workflow. Dense but every paragraph earns its place; the failure-triage paragraph is the longest and slightly discursive, though still actionable.

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?

Covers the mutation's external effect, preconditions, and user-confirmation requirement; return values needn't be explained because an output schema exists. Only the workspace_id/post_id parameter semantics are unaddressed.

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 description coverage is 0%, so the description must carry the load, and it explains the two non-obvious parameters well: publish_now=true for immediate publish, scheduled_at as a future ISO-8601 time WITH a timezone offset, and that exactly one must be supplied. post_id and workspace_id are left to inference, which is a minor gap.

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+resource ('Publish a post that failed again') with the two mutually exclusive modes spelled out, and the eligibility constraint (only status "failed"). It is clearly distinguishable from list_scheduled_posts and cancel_scheduled_post, which are named.

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 an explicit workflow: locate the post via list_scheduled_posts(status=["failed"]), read publish_error, tell the user the reason first, retry only when the failure was transient, and route to cancel_scheduled_post when the post should not go out. It also states the when-not conditions (expired Instagram connection, rejected media) that make retrying useless.

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