Skip to main content
Glama

delete_comment

DestructiveIdempotent

Permanently delete one review comment and all of its replies, with confirm: true. Cannot be undone; resolving a comment (edit_comment) keeps it instead.

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": {
      "survey_id": "<survey_id>",
      "comment_id": "<comment_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Deleting a comment is permanent, including any replies to it.
survey_idYesSurvey UUID (for read-back context)
comment_idYesComment UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is structured data; the description still adds real value by disclosing the cascade (replies are also deleted) and the irreversibility ('cannot be undone'). It does not describe the failure mode if confirm is false or the response body, which keeps it from a 5.

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 sentences, front-loaded with the action and scope, followed by the irreversibility and the alternative. No filler or redundant restatement of the name.

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 destructive single-resource delete with a full schema, output schema, and destructive annotations, the description covers scope, cascade, irreversibility, mandatory confirmation, and the safer alternative. Nothing needed to call it correctly 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 adds meaning by tying comment_id to a cascade over its replies and by emphasizing the confirm gate as mandatory rather than optional. That is genuine semantic value beyond the field descriptions.

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 with scope ('one review comment and all of its replies'), and explicitly marks it as permanent versus the non-destructive sibling edit_comment. An agent can distinguish it from deletion siblings (delete_block, delete_question) by resource alone.

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 explicitly ('resolving a comment (edit_comment) keeps it instead') and states the precondition 'with confirm: true'. That gives both the when-to-use-this and the when-to-use-the-other condition in a single clause.

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