Skip to main content
Glama

delete_comment

DestructiveIdempotent

Permanently delete a comment from the account's post. There is no undo — to take one out of view reversibly use hide_comment. Confirm with the user, naming the comment, before calling it.

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>",
      "ig_account_id": "<ig_account_id>",
      "comment_id": "<comment_id>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYes
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes
reply_idNo
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly supplied; the description still adds the crucial fact that deletion is irreversible ('no undo') and imposes a human-confirmation step. It does not describe the response payload, but an output schema exists to cover that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the destructive nature, followed by the alternative and the confirmation requirement. Every clause carries operational weight; nothing is redundant.

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 three-parameter mutation, the description covers the highest-risk information (irreversibility, alternative, confirmation) and an output schema exists so return values need not be explained. The one remaining hole is the meaning of the three ID parameters, which neither schema nor description documents.

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

Parameters2/5

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

Schema description coverage is 0% for three required identifiers (workspace_id, ig_account_id, comment_id). The description only alludes to 'a comment' and 'the account's post', leaving workspace_id entirely unexplained and giving no format or sourcing hints for the other two, so it fails to compensate for the coverage gap.

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 ('Permanently delete') and resource ('a comment from the account's post'), and explicitly contrasts with the reversible sibling hide_comment. An agent can distinguish it from list_comments or hide_comment without opening a 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?

Names the alternative (hide_comment) and the condition selecting it (when the removal must be reversible), and adds a mandatory pre-call workflow: confirm with the user, naming the comment. That is explicit when-to-use, when-not-to-use, and prerequisite guidance.

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