Skip to main content
Glama

posterly

by ly.poster
OverviewDiscussionsAdmin

delete_post

DestructiveIdempotent

Delete posts. DESTRUCTIVE and IRREVERSIBLE. post_id: delete one post; fetch it with get_post first, confirm what will be deleted, then pass confirm=true. A post that is currently publishing is never deleted. A published post is taken down only when the user also explicitly confirms the live removal: delete_mode=platform with confirm_published=true takes the live post down too; delete_mode=posterly removes only the posterly record and leaves it up. Live deletion supports eligible connected platforms with saved post IDs and deletion permissions; refusals keep the record. Threads requires threads_delete. YouTube requires youtube.force-ssl or equivalent, upload alone is insufficient. A published post with no live URL and no platform id is removed from posterly only. group_id: delete every draft, scheduled, failed, or paused post matching a caller-defined group_id, post_group_id, api_group_id, or release_id. A group delete never removes published posts. Preview then confirm: call without confirm to get a preview and preview_id, show it, then call again with confirm=true and that preview_id.

Input Schema

NameRequiredDescriptionDefault
confirmNopost_id: true after the user explicitly confirms the deletion. group_id: Leave out to get a preview. Set true only after the user explicitly approved it, with the preview_id.
post_idNoDelete this one post.
group_idNoDelete every unpublished post in this group or release instead. Never deletes published posts.
preview_idNoThe preview_id from the preview call. Required with confirm: true for actions that preview first.
delete_modeNoRemove the posterly record only, or also take down the live post.
confirm_publishedNoWith post_id only. True only after the user explicitly confirms taking a live post down. Required with delete_mode=platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"post_id: true after the user explicitly confirms the deletion. group_id: Leave out to get a preview and preview_id. Set true only after the user explicitly approved the preview, together with preview_id."New value: +"post_id: true after the user explicitly confirms the deletion. group_id: Leave out to get a preview. Set true only after the user explicitly approved it, with the preview_id."
    • changedInput schema / properties / confirm_published / description
      Previous value: -"With post_id only. True only after the user explicitly confirms taking a live post down. Required with delete_mode=platform. Use delete_mode=posterly to leave the live post up."New value: +"With post_id only. True only after the user explicitly confirms taking a live post down. Required with delete_mode=platform."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: publishing posts are never deleted, published posts go down only with delete_mode=platform plus confirm_published=true, posterly-only leaves the live post up, live deletion requires eligible platforms and permissions (threads_delete, youtube.force-ssl), and refusals keep the record. This is exactly the operational context annotations cannot convey.

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 destructive warning and the two deletion modes, and nearly every sentence carries operational detail. It is dense but warranted for a conditional destructive tool, with only minor room for tightening.

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?

Covers prerequisites, permission requirements, the preview/confirm workflow, per-mode behavior, and refusal handling for a destructive mutation with no output schema. An agent has everything needed to invoke it safely.

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 real meaning: delete_mode=platform pairs with confirm_published, confirm requires preview_id for previewing actions, and group_id matches caller-defined group_id/post_group_id/api_group_id/release_id. It explains parameter interdependencies beyond the schema's per-field text.

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?

Starts with a specific verb+resource ('Delete posts') immediately flagged DESTRUCTIVE and IRREVERSIBLE, then splits cleanly into the post_id and group_id modes. An agent can distinguish it from get_post/update_post without opening the schema.

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?

Explicitly routes usage: single post via post_id requires fetching first with get_post and confirming, bulk via group_id matches drafts/scheduled/failed/paused only, and the preview-then-confirm flow is spelled out. The prerequisite (get_post) and the alternative (group_id) are both named.

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

All posterly 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