Skip to main content
Glama
Hermoso

Hermoso

Official

Retry a failed scheduled post

retry_scheduled
Destructive

Resend only the channels of a scheduled post that failed to publish, optionally correcting fields like board, page, or caption in the same call, without duplicating posts that already went out.

Instructions

Send a post that FAILED again. A scheduled post fans out across its channels INDEPENDENTLY, so a failure is usually PARTIAL — LinkedIn 401s while Instagram published fine — and this re-fires ONLY the channels that did not succeed by default (list_scheduled reports them as retryable). It re-queues the same content as a NEW post that goes out RIGHT AWAY — the queue picks it up on its next pass, within seconds — and the original keeps its failure record so the history still shows what went wrong. Naming a channel that already published is REFUSED rather than quietly posting a second time. Two independent belts stop a double-post: a channel that genuinely published can only REPLAY (nothing is posted), and a channel whose outcome is UNRESOLVED — the platform timed out and may be holding the post — refuses with that reason instead of guessing. Retry after fixing the cause — and you can fix it IN THIS CALL: pass boardId, pageId, linkedinOrganizationId, locationId, message or captions to correct the value that failed, and the corrected post is re-validated exactly like a fresh schedule. That matters because the commonest cause is a field, not an outage: a Pin aimed at the wrong board fails identically however many times it is re-sent. Anything you do not name is copied from the original. To send the same thing again ON PURPOSE, use duplicate_scheduled.

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": {
      "id": "<id>"
    },
    "name": "retry_scheduled"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNohold the retry until a later time — ISO timestamp or epoch milliseconds. Leave it out to retry immediately, which is almost always what you want. A time you name here must be at least a minute from now, exactly like any other scheduled post.
idYesthe scheduled post id from list_scheduled
brandNoWHICH PROFILE this post is in — id or exact name from list_brands; needed when it is not the profile this connection is pinned to. A name that matches no profile, or two, is REFUSED.
chatIdNoCORRECT THE TELEGRAM DESTINATION on retry — the @username or numeric id of the chat. A post aimed at a chat the bot is not in fails every time it is retried until this changes.
pageIdNoCORRECT THE PAGE on retry — which connected Facebook Page (and its linked Instagram/Threads) publishes, from list_meta_pages.
boardIdNoCORRECT THE BOARD on retry — the Pinterest board the Pin goes on, from list_pinterest_boards. A Pin aimed at a board Pinterest refuses fails the same way on every retry until this is changed.
messageNoCORRECT THE CAPTION on retry — use this when the original was refused for length or content. Anything not named here is copied from the original post.
captionsNoCORRECT ONE CHANNEL’S CAPTION on retry, e.g. { "x": "..." } when only that channel refused the text.
channelsNoretry only these channels (default: every channel that did not publish)
locationIdNoCORRECT THE LISTING on retry — which Google Business Profile location, e.g. "locations/123" from list_business_locations.
allowDuplicateNoONLY for a channel you have checked by hand and confirmed the post is genuinely NOT there. It bypasses the double-post protection and can publish a second public copy, so never set it to work around a refusal you have not investigated.
whopExperienceIdNoWHOP — correct the forum or chat on retry (exp_…, from list_whop_destinations).
linkedinOrganizationIdNoCORRECT THE LINKEDIN AUTHOR on retry — the company Page id from list_linkedin_pages. Set it to an empty string to fall back to the personal profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.571
    • changedInput schema / properties / channels / items / enum
      Previous value: -[
      -  "facebook",
      -  "instagram",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "linkedin",
      -  "x",
      -  "pinterest",
      -  "google_business",
      -  "bluesky",
      -  "telegram",
      -  "wordpress",
      -  "discord",
      -  "slack",
      -  "whop"
      -]New value: +[
      +  "facebook",
      +  "instagram",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "linkedin",
      +  "x",
      +  "pinterest",
      +  "google_business",
      +  "bluesky",
      +  "telegram",
      +  "wordpress",
      +  "discord",
      +  "slack",
      +  "whop",
      +  "shopify_blog",
      +  "webflow",
      +  "wix"
      +]
  2. Changed2 schema fields changedv0.1.519
    • changedInput schema / properties / channels / items / enum
      Previous value: -[
      -  "facebook",
      -  "instagram",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "linkedin",
      -  "x",
      -  "pinterest",
      -  "google_business",
      -  "bluesky",
      -  "telegram"
      -]New value: +[
      +  "facebook",
      +  "instagram",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "linkedin",
      +  "x",
      +  "pinterest",
      +  "google_business",
      +  "bluesky",
      +  "telegram",
      +  "wordpress",
      +  "discord",
      +  "slack",
      +  "whop"
      +]
    • addedInput schema / properties / whopExperienceId
      Added value: +{
      +  "description": "WHOP — correct the forum or chat on retry (exp_…, from list_whop_destinations).",
      +  "type": "string"
      +}
  3. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post is in — id or exact name from list_brands; needed when it is not the brand this connection is pinned to. A name that matches no brand, or two, is REFUSED."New value: +"WHICH PROFILE this post is in — id or exact name from list_brands; needed when it is not the profile this connection is pinned to. A name that matches no profile, or two, is REFUSED."
  4. Changed1 schema field changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post is in — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED."New value: +"WHICH BRAND this post is in — id or exact name from list_brands; needed when it is not the brand this connection is pinned to. A name that matches no brand, or two, is REFUSED."
  5. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND this post is in — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED.",
      +  "type": "string"
      +}
  6. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description earns its keep by explaining exactly why and how that risk is bounded — the original retains its failure record, already-published channels can only REPLAY, unresolved channels refuse with a reason, and allowDuplicate bypasses protection at the cost of a second public copy. This is materially more than the annotation flags convey.

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?

Despite its length, every sentence carries a distinct fact — partial fan-out, new-post semantics, double-post guards, in-call correction, and sibling routing — and the most decision-relevant information (what gets retried) comes first. Capitalized emphasis is used sparingly and on the words an agent must not misread.

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 13-parameter, destructive, open-world tool this covers failure modes, correction options, and safety rails thoroughly. The gap is the return side: with no output schema, the description never says what comes back (new post id, per-channel outcome) or how to confirm the retry landed, leaving the agent to infer it from list_scheduled.

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%, so baseline is 3; the description adds the crucial rule that anything not named is copied from the original, and frames the correction parameters as fixes applied to the failed value. It also notes the default channel set (every non-published channel), which the schema states but the description reinforces in context. It does not add format or validation detail beyond what the schema already documents, keeping it short of a 5.

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?

The first sentence gives a specific verb and resource ("Send a post that FAILED again") and the description immediately scopes it as a partial-channel re-fire rather than a full repost. It explicitly contrasts with duplicate_scheduled at the end, so an agent can distinguish the two without opening either 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?

It states when to use (after fixing the cause, for channels reported as `retryable` by list_scheduled) and when not to (intentional re-sends belong to duplicate_scheduled, and naming an already-published channel is refused, not silently duplicated). The prerequisite that the commonest failure is a bad field is called out, which changes how an agent should approach the call.

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

Deploy Server

Other Tools