Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_delete_comments

Destructive

Deletes an explicit list of Figma comment IDs (up to 100) from a file and reports partial failures, skipped duplicates, and replies removed with root comments.

Instructions

DESTRUCTIVE WRITE: sequentially delete only an explicit list of comment IDs (max 100). Root deletion may remove replies. Duplicate IDs and children covered by successful roots are skipped. Partial failures are reported; authentication or rate limits stop remaining writes. Requires explicit user authorization.

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": {
      "file": "<file>",
      "commentIds": "<commentIds>"
    },
    "name": "figma_delete_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
commentIdsYes

Output Schema

NameRequiredDescriptionDefault
fileKeyYes
resultsYes
completeYes
duplicateCommentIdsYes
requestedCommentIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive, non-idempotent, openWorld) by disclosing sequencing, cascading reply deletion under root comments, duplicate/child skipping, partial-failure reporting, and that auth or rate-limit errors abort remaining writes. The 'Requires explicit user authorization' note adds a real operational prerequisite for a destructive operation.

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?

The destructive warning is front-loaded in capitals, and each following sentence carries a distinct behavioral fact. No filler or restatement of the title.

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 batch tool, the failure, ordering, and cascade semantics are well covered, and an output schema exists so return-value detail is unnecessary. The only gap is the undocumented 'file' identifier, which matters for making a correct first call.

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 description coverage is 0%, so the description must carry the load. It explains commentIds thoroughly (explicit IDs, 100 cap, duplicate and child de-duplication), but says nothing about the required 'file' parameter or its expected format, leaving half the inputs undocumented.

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 ('sequentially delete ... comment IDs') plus a precise scope ('only an explicit list', 'max 100'), which clearly distinguishes it from the singular figma_delete_comment sibling. An agent can identify the batch-vs-single distinction without opening either schema.

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?

Establishes the operative condition clearly: it deletes only explicitly supplied IDs, so callers cannot express filter- or thread-based bulk deletion here. It does not explicitly name figma_delete_comment as the alternative for a single ID, leaving that routing to inference.

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