Skip to main content
Glama

Delete Comment

delete_comment
DestructiveIdempotent

Delete a comment that an agent posted on behalf of the signed-in user (from any of their connections). You cannot delete comments people wrote themselves, or comments by anyone else. The comment is replaced by a "deleted" marker.

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": {
      "slug": "<slug>",
      "id": "<id>"
    },
    "name": "delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a comment an agent posted for you
slugYesThe document slug (e.g. "abc12345" from the document URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 covered. The description still adds real behavioral context beyond them: the effect is a soft delete ('The comment is replaced by a "deleted" marker') and the authorization boundary is limited to agent-posted comments across all of the user's connections. It stops short of saying whether failure on an ineligible comment is an error or a no-op, which a caller might want to know.

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?

Three short sentences, no redundancy: what is deleted, the eligibility restriction, and the resulting state. The most consequential constraint (ownership scope) is front-loaded in the first sentence.

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 two-parameter destructive tool with no output schema and full annotation coverage, the description supplies what the structured data cannot: who is entitled to delete what, and what the resulting state looks like. The only residual gap is the behavior on an unauthorized or already-deleted target, which is minor given idempotentHint=true.

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 100% and both parameters already carry descriptions ('The id of a comment an agent posted for you', 'The document slug ... from the document URL'). The prose adds no syntax, format, or edge-case guidance beyond that, so the baseline 3 applies.

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?

The description gives a specific verb and resource ('Delete a comment') and narrows it to 'a comment that an agent posted on behalf of the signed-in user (from any of their connections)', which is far more precise than the tool name alone. It is unambiguously distinguishable from add_comment and list_comments, which are the natural confusable siblings.

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?

It clearly states the exclusion condition: 'You cannot delete comments people wrote themselves, or comments by anyone else', so an agent knows when this tool will fail. What is missing is an explicit forward reference — e.g., which sibling to use when the comment is not agent-authored — but the positive eligibility criteria are explicit.

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.