Skip to main content
Glama
Sign In

Octopost

by ink.octopost
OverviewDiscussionsAdmin

Delete a post

delete_post
DestructiveIdempotent

Delete a post from Octopost. For published posts, also attempts to delete from each platform via their APIs.

Platform deletion support:

  • Twitter: Full API deletion supported.

  • Bluesky: Full API deletion supported (deleteRecord).

  • LinkedIn: Full API deletion supported.

  • Mastodon: Full API deletion supported.

  • Threads: API deletion not supported — returns the post URL so the user can delete manually.

The post is ALWAYS removed from Octopost's database regardless of platform deletion results.

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": {
      "post_id": "<post_id>"
    },
    "name": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post ID (UUID) to delete.
delete_from_platformsNoWhether to also delete from platforms (for published posts). Default: true. Set to false to only remove from Octopost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds substantial context beyond them: a per-platform deletion support matrix, the Threads exception with its manual-delete URL fallback, and the guarantee that the Octopost record is removed regardless of platform outcomes. This lets an agent predict partial-failure behavior before invoking.

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?

Front-loaded with the core action and outcome guarantee, then a scannable bulleted platform breakdown. The bullets are longer than strictly necessary for the four fully-supported platforms, but each conveys a distinct capability boundary, so little is wasted.

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 a destructive, cross-system tool with no output schema, the description covers the critical unknowns: what gets destroyed, what may fail per platform, and what happens to the Octopost record on partial failure. Nothing an agent needs before calling 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 the baseline is 3, but the description adds meaning by scoping delete_from_platforms to published posts and clarifying that the database removal happens unconditionally. The interaction between the flag and platform results is explained rather than left implicit in the schema.

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?

States a specific verb and resource ("Delete a post from Octopost") and immediately extends it to the external effect ("also attempts to delete from each platform via their APIs"). No sibling tool performs deletion, so the scope is unambiguous against the rest of the toolset.

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?

The description makes the use condition clear: published posts trigger cross-platform deletion, and the delete_from_platforms flag lets the caller restrict the operation to Octopost only. It does not name alternative tools (e.g., update_post, cancel_scheduled) or state explicit when-not-to-use conditions, so it falls short of a 5.

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

All Octopost toolsInspect
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.

Resources