Skip to main content
Glama

Delete a comment

delete_comment
DestructiveIdempotent

Permanently delete one comment from a video, after confirming it with the user. Requires a Pro account and video, comment, and confirm IDs.

Instructions

Recordful Pro only (check get_status recorder.account.plan first). Delete one comment from a video (get_video_activity lists them with their ids). Its author can, and so can the person who recorded the video or the workspace owner. It can't be brought back: show the user the comment and wait for their yes, then call with confirm: true.

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

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true, and only after the user has confirmed deleting this exact comment.
videoIdYesThe video the comment is on. Required.
commentIdYesThe comment to delete (from get_video_activity).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds the consequences that matter: the deletion is irreversible ('It can't be brought back') and must be preceded by showing the user the comment and getting a yes. It also discloses authorization scope and plan requirements, which annotations cannot express.

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?

Four sentences, each carrying distinct load: plan gate, target/scope, permissions, and the destructive-confirmation protocol. Parenthetical references are dense but front-loaded and purposeful; minor compression is possible but nothing 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 destructive three-parameter mutation with no output schema, the definition covers everything an agent needs: prerequisite lookup, permission rules, irreversibility, and the exact confirmation gate. Nothing required to call it safely 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, but the description adds real meaning: it tells the agent where commentId comes from (get_video_activity) and frames confirm as a gated action contingent on explicit user approval rather than a mere boolean. It does not add format detail for videoId beyond the schema's pattern.

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 — 'Delete one comment from a video' — with explicit scope ('one comment'). It also distinguishes itself from siblings by naming get_video_activity as the source of comment ids and comment_on_video implicitly as the non-destructive counterpart.

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 gates usage on plan ('Recordful Pro only (check get_status recorder.account.plan first)') and on obtaining ids via get_video_activity. It also spells out the who-can-delete rule (author, video recorder, workspace owner) and the required confirmation sequence before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.