Skip to main content
Glama

Delete Social Post

delete_social_post
DestructiveIdempotent

[write] Delete a post from selieeai. WARNING: by default this removes ONLY the selieeai record - a post already live on the platform stays there (and tg messages stay in the chats). platform = ig|fb|tw|tt|yt|li|th|tg|bsky; post_id = _post_id, or pass post_uuid. remote=true also deletes the live post on the platform itself, but only fb|tw|yt|bsky support that (ig|tt|li|th|tg have no delete API, remote is ignored there); if the platform refuses, nothing is deleted. A post being sent/uploaded cannot be deleted.

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": {
      "platform": "<platform>"
    },
    "name": "delete_social_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteNo
post_idNo
platformYes
post_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructive/openWorld/idempotent, but the description adds substantive behavior beyond them: that tg messages stay in chats, that a platform refusal results in nothing being deleted, and that in-flight uploads are undeletable. These are exactly the side-effect and failure-mode facts an agent needs before a destructive call.

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?

Dense and front-loaded – the WARNING about the default being local-only appears before the parameter details, which is the right ordering for a destructive tool. It is long, but nearly every clause carries a distinct constraint; only the parenthetical about tg messages feels slightly tacked on.

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 destructive, multi-platform mutation with no output schema, the description covers what is destroyed, platform support, silent-ignore behavior, and failure semantics. Remaining omissions are return value shape and any permission/scope requirements, which matter but are secondary.

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 0%, so the description carries the full burden and does so: it enumerates the platform values (ig|fb|tw|tt|yt|li|th|tg|bsky), explains post_id format versus post_uuid, and defines remote. It does not state precedence when both post_id and post_uuid are supplied, and the '<platform>_post_id' phrasing sits awkwardly against the integer typing 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+resource ('Delete a post') and immediately disambiguates what is actually deleted: the local selieeai record only by default, versus the live platform post with remote=true. An agent can tell exactly what this does 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 Guidelines4/5

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

Explicit conditions are given for the two modes: default removes only the local record, remote=true removes the live post but only on fb|tw|yt|bsky, and is silently ignored elsewhere. It also states a post being sent/uploaded cannot be deleted. It does not name any sibling tool to use instead, which is the only remaining gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.