Skip to main content
Glama

delete_inbox_comment

Destructive

Permanently delete a comment on one of the workspace's posts, on the platform and from the inbox: a comment someone left, or a reply the workspace's own account posted (for example one sent under the wrong comment). Facebook, Instagram and TikTok comments only. On TikTok only replies the workspace's own account posted: TikTok and YouTube do not let an account delete comments other people left, so use hide_inbox_comment for those. Replies under the comment are deleted with it. When the account's last reply under a comment is deleted, that comment counts as unanswered again and get_next_unanswered serves it. This cannot be undone: confirm with the user before calling. Takes the message id (the #id in the thread), not the conversation id. A 403 reconnect_required means the account must be reconnected in the dashboard to grant the moderation permission.

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": {
      "message_id": "<message_id>"
    },
    "name": "delete_inbox_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe inbox message id of the comment (the #id in the thread)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description builds well past that: replies are deleted with the parent, the comment reverts to unanswered and re-enters get_next_unanswered, the action is irreversible, and a 403 reconnect_required signals a dashboard reconnect is needed. These are consequences an agent cannot infer from annotations alone.

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 with the destructive warning and platform scope arriving before the edge cases. It is a single run-on block rather than separated clauses, but essentially every sentence adds a distinct operational fact and none is filler.

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 one-parameter destructive tool with no output schema, the description covers platform eligibility, cascade effects, downstream state changes, irreversibility, the required id format, and the auth failure mode. Nothing an agent needs before invoking it 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; the description earns an extra point by disambiguating the identifier ('the #id in the thread, not the conversation id'), which prevents a realistic misuse of the single required parameter.

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 ('Permanently delete a comment on one of the workspace's posts, on the platform and from the inbox') and immediately bounds the resource by platform (Facebook, Instagram, TikTok only). It distinguishes itself from the sibling hide_inbox_comment by naming it as the fallback where deletion is impossible.

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 names when to use this versus the alternative: 'TikTok and YouTube do not let an account delete comments other people left, so use hide_inbox_comment for those.' It also covers the self-authored reply case and instructs the agent to confirm with the user before calling.

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