Skip to main content
Glama

Retry Failed Platforms

retry_failed_platforms
Destructive

Re-queue publishing for a post's FAILED platforms. platformIds takes platformId values from list_post_results, platform names such as "BLUESKY" (every failed row of that platform), or can be omitted to retry every failed row. Only rows with status FAILED are reset to PENDING and retried with the same content. A value matching neither a row id nor a platform of the post fails with "Unknown retry target"; with nothing failed among the matches the call fails with "No failed platforms to retry". The post moves to PUBLISHING and the retry is asynchronous, so check list_post_results for the outcome. Read each errorMessage first and retry once the cause is fixed (reconnected account, replaced media), not for a platform-side restriction, which will just fail again. Content cannot change on retry. Returns { postId, queuedPlatforms, isScheduled: false }.

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_failed_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID whose platforms failed
platformIdsNoplatformId values from list_post_results or platform names such as "BLUESKY". Omit to retry every FAILED row
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with postId, queuedPlatforms (platforms re-queued for publishing), and isScheduled: false. Outcomes arrive asynchronously in list_post_results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / result / properties / isScheduled / description
      Added value: +"Always false: the retry publishes now; list_post_results shows each outcome"
    • changedOutput schema / properties / result / properties / isScheduled / type
      Previous value: -[
      -  "boolean",
      -  "null"
      -]New value: +"boolean"
    • addedOutput schema / properties / result / properties / postId / description
      Added value: +"The post whose platforms were re-queued"
    • changedOutput schema / properties / result / properties / postId / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedOutput schema / properties / result / properties / queuedPlatforms / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "description": "One of: FACEBOOK, INSTAGRAM, THREADS, TIKTOK, TWITTER, BLUESKY, LINKEDIN, PINTEREST, YOUTUBE, MASTODON, TELEGRAM, GOOGLE_BUSINESS, TUMBLR, WORDPRESS",
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / result / properties / queuedPlatforms / description
      Added value: +"Platform names, such as BLUESKY, queued to publish again"
    • addedOutput schema / properties / result / properties / queuedPlatforms / items
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / result / properties / queuedPlatforms / type
      Added value: +"array"
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "postId",
      +  "queuedPlatforms",
      +  "isScheduled"
      +]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "isScheduled": {
      +    "type": [
      +      "boolean",
      +      "null"
      +    ]
      +  },
      +  "postId": {
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "queuedPlatforms": {
      +    "anyOf": [
      +      {
      +        "items": {
      +          "description": "One of: FACEBOOK, INSTAGRAM, THREADS, TIKTOK, TWITTER, BLUESKY, LINKEDIN, PINTEREST, YOUTUBE, MASTODON, TELEGRAM, GOOGLE_BUSINESS, TUMBLR, WORDPRESS",
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  3. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another"New value: +"Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another"
  5. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • changedInput schema / properties / platformIds / description
      Previous value: -"platformId values of FAILED rows from list_post_results (not platform names). At least one"New value: +"platformId values from list_post_results or platform names such as \"BLUESKY\". Omit to retry every FAILED row"
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "platformIds"
      -]New value: +[
      +  "id"
      +]
  7. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Post ID"New value: +"Post ID whose platforms failed"
    • changedInput schema / properties / platformIds / description
      Previous value: -"Failed platform IDs to retry"New value: +"platformId values of FAILED rows from list_post_results (not platform names). At least one"
    • changedOutput schema / properties / result / description
      Previous value: -"The retry outcome for the requested platform IDs as returned by the AdaptlyPost API."New value: +"An object with postId, queuedPlatforms (platforms re-queued for publishing), and isScheduled: false. Outcomes arrive asynchronously in list_post_results."
  8. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=false, openWorld=true, and the description adds real behavior on top: only FAILED rows are reset to PENDING, retried with identical content, the post transitions to PUBLISHING, and execution is asynchronous. It could go further on whether the retry consumes quota or how repeated async attempts interact, but the disclosed behavior is unusually rich.

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?

Dense but well ordered: purpose, then retry-target semantics, then failure cases, then the async/errorMessage caveat. No filler sentences, though the final return-shape sentence is somewhat crammed onto an already long paragraph.

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 destructive, non-idempotent, async mutation this covers scope, targeting, error conditions, and follow-up verification, which is nearly everything an agent needs. The one redundancy is restating the response fields ({ postId, queuedPlatforms, isScheduled }) despite an output schema already existing.

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, and the description earns above that by explaining the overload of platformIds (row ids from list_post_results, platform names matching all failed rows of that platform, or omitted for all) plus its failure mode "Unknown retry target." This is meaning the schema's type/subtype alone cannot convey.

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?

Opens with a specific verb+resource: "Re-queue publishing for a post's FAILED platforms." That immediately distinguishes it from siblings like get_post, list_post_results, or create_post, and the FAILED-only scope is stated up front rather than buried.

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 explicit when-to-use and when-not-to-use guidance: read each errorMessage first and retry only after fixing the cause (reconnected account, replaced media), but not for a platform-side restriction "which will just fail again." It also points to list_post_results for both target ids and outcome checking.

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