Skip to main content
Glama

Delete a comment

delete_comment
DestructiveIdempotent

Deletes a comment from the network for good. Instagram and Facebook Pages: any comment on the account's post. YouTube, X, LinkedIn company Pages, Bluesky and Mastodon: only the account's own comments and replies (hide others instead where hiding exists). Threads: not available (Shager doesn't hold Threads' delete permission). On X it is billed to the workspace's monthly X limit. Cannot be undone, so a person approves each deletion in Shager first: the first call answers needs_confirmation with confirm_url; after your human approves, make the same call again. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "post_id": "<post_id>",
      "channel_id": "<channel_id>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
channel_idYes
comment_idYes
workspace_idYesWorkspace id from list_workspaces
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmation_token
      Added value: +{
      +  "description": "The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructive/idempotent annotations: state that deletion is permanent, that a human approval gate makes the first call return needs_confirmation with confirm_url and a re-call complete it, and that X deletions consume the workspace's monthly X limit. That is exactly the operational context annotations cannot carry.

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?

Effect-independent and front-loaded: what it deletes, where it's restricted, then cost, then the confirmation flow. Parenthetical asides are dense but each carries real constraint information; only minor compaction is possible.

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?

With no output schema, the description still tells the agent what to expect back (needs_confirmation plus confirm_url) and the exact retry protocol, plus platform-specific limits. Nothing an agent needs to invoke this destructive tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%, so the description has to compensate, and it partly does by explaining the confirmation_token round-trip (first call yields it, same call again passes it). It says nothing about what post_id, channel_id, or comment_id must reference, so half the parameters still rely on the bare 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 ("Deletes a comment") and immediately scopes it per network: any comment on the account's post for Instagram/Facebook Pages, only the account's own comments on YouTube, X, LinkedIn, Bluesky and Mastodon. The reader knows exactly what the tool acts on and how that differs from a generic delete.

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?

Explicit when-not guidance is given: Threads is unsupported (no delete permission), other users' comments on most networks cannot be deleted and "hide others instead where hiding exists" routes the agent toward the hide_comment sibling. Unclaimed sandbox exclusion further narrows applicability.

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.

Resources