GoodSender

Re-announce Post

reannounce_post

Destructive

Post a published post to one Announce destination (X, LinkedIn, Bluesky or Mastodon) again — the only way to announce twice, and the retry for an announce that failed. A publish never announces a post twice on its own.

This posts publicly in the user's name, and a second post on the same platform cannot be recalled from GoodSender. The destination must be selected in the post's distribution, connected, and the post must have a public address to link to; the announce is queued and its outcome appears on get_post_distribution. Plan lists the exact text and link that will be posted.

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>",
      "Destination": "<Destination>"
    },
    "name": "reannounce_post"
  }
}

Input Schema

Name	Required	Description	Default
`PostID`	Yes	Published post id.
`Destination`	Yes	The Announce destination to post to again: x, linkedin, bluesky or mastodon.

Output Schema

Name	Required	Description
`Plan`	Yes	Exactly what will be posted, and where.
`Result`	Yes	OK once it is queued. On a local server with action guards on, the pending-confirmation notice while the re-announce awaits approval.
`Distribution`	Yes	The post's distribution: as reviewed while awaiting confirmation, re-read once queued.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations that already mark this as destructive, open-world, and non-idempotent, the description adds critical behavioral context: it posts publicly in the user's name, a second post cannot be recalled, and the outcome appears on get_post_distribution. This materially improves the agent's ability to avoid or plan around destructive side effects.

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?

The description is front-loaded with the core action and the key distinction from publish, then adds warning and prerequisites. Every sentence carries operational value, with no repetition of the schema or annotations.

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?

Given an output schema and detailed annotations, the description supplies the remaining operational context an agent needs: public visibility, irreversibility, prerequisites, queuing behavior, and where to check the result. Nothing important for correct invocation is missing.

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 both parameters are documented structurally. The description still adds useful semantic constraints, especially that the Destination must be selected in the post's distribution and connected, and that the PostID must correspond to a post with a public address.

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 description states a specific verb and resource: re-posting a published post to one Announce destination. It explicitly distinguishes this from publish by saying a publish never announces a post twice on its own, and identifies it as the retry path for failed announces.

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 gives explicit when-to-use conditions: the only way to announce twice, and the retry for an announce that failed. It also names prerequisites, including destination selection, connection, and public address, leaving little inference for the agent.

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

All GoodSender 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.