Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

retry_post

Retry publishing a post to only the channels that failed, using its post ID, so partial or failed social media publishing can be completed.

Instructions

Retry publishing failed channels for a post that partially or fully failed.

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

NameRequiredDescriptionDefault
postIdYesThe post ID returned from post_text, post_image, or post_video

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: only failed channels are retried, not the ones that already succeeded. It omits other relevant behavior such as whether the retry is idempotent, what permissions are required, and what happens if no channel actually failed.

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?

A single, front-loaded sentence with no filler; the operation and its target condition are stated immediately. It is appropriately sized for a one-parameter tool.

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 simple one-required-parameter tool with full schema coverage and no output schema, the definition covers what it does and when it applies. Minor gaps remain around return behavior (per-channel results) and edge cases like a post with no failed channels, but nothing essential is missing for correct invocation.

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 100% and the single parameter is already documented as the post ID returned by post_text, post_image, or post_video. The description reinforces that the ID identifies the post whose failed channels are retried, adding a small amount of scoping meaning beyond the schema text.

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 names a specific verb ("Retry publishing") and a specific resource scope ("failed channels for a post"), so an agent knows exactly what operation it performs. It does not explicitly distinguish itself from siblings like check_post_status or publish_draft, which keeps it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "for a post that partially or fully failed" implies the triggering condition, so usage is inferable. However, it never states when not to use it (e.g., when nothing failed, or when the post should be republished via publish_draft) and names no alternative tool for checking status first.

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