RepeatPost

Delete a post

deletePost

DestructiveIdempotent

Delete a draft, scheduled or published social media post by uuid; the workspace role has to allow deletion. Deletes one channel's post only: posts created together for several channels share a postGroupUuid, and the rest of that group is unaffected. By default the post is removed from RepeatPost only and stays live on the social platform. With deleteOnPlatform true it is also deleted on the platform, which removes the real post and its engagement and cannot be undone.

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": {
      "postUuid": "<postUuid>"
    },
    "name": "deletePost"
  }
}

Input Schema

Name	Required	Description	Default
`postUuid`	Yes	Post uuid
`deleteOnPlatform`	No	Also delete the post on the social platform. Irreversible, and OWNER-only: an ADMIN still gets the local delete, and remote.outcome reports that the platform half was skipped. Defaults to false.

Output Schema

Name	Required	Description	Default
`error`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations' destructive/idempotent flags, it discloses the key behavioral nuance: the default is a local-only removal that leaves the post live on the platform, while deleteOnPlatform removes the real post and its engagement irreversibly. It also flags the OWNER vs ADMIN asymmetry, which the annotations do not 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?

Three tight sentences, each carrying distinct load: scope/role, single-post-vs-group semantics, then the default and destructive escalation. The most consequential information (platform deletion is irreversible) is placed at the end where it lands hardest.

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?

For an irreversible delete with an output schema present, the description covers everything the agent needs before calling: valid target states, permission gate, blast radius, and the consequence of the optional flag. Return-value detail is correctly left to the output schema (it even references remote.outcome).

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%, so baseline is 3, but the description adds interpretive meaning the schema lacks: what the default (false) actually means operationally and the irreversibility/auth constraint attached to setting it true. postUuid itself is only restated, not enriched.

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?

Specific verb (delete) plus resource (a draft, scheduled or published social media post) and the identifier (uuid). It also carves out its scope against the sibling deletePostGroup by stating it deletes one channel's post only and leaves the rest of the postGroupUuid group unaffected.

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

Usage Guidelines4/5

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

Gives a real prerequisite (the workspace role must allow deletion) and a clear condition for the higher-impact mode (deleteOnPlatform true). The group-vs-single-post distinction strongly implies deletePostGroup is the alternative, though that sibling is never named explicitly, so routing is left slightly to inference.

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

All RepeatPost tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.