Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_delete_reaction

Destructive

Remove your own emoji reaction from a specific Figma comment by supplying the file, comment ID, and exact emoji shortcode. Use it to undo a reaction you added.

Instructions

WRITE: remove only the authenticated user's specified reaction from an explicit Figma comment. Supply the exact emoji shortcode. Requires 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>",
      "commentId": "<commentId>",
      "emoji": "<emoji>"
    },
    "name": "figma_delete_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
emojiYes
commentIdYes

Output Schema

NameRequiredDescriptionDefault
emojiYes
actionYes
fileKeyYes
successYes
commentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral facts: it is a write, it only affects the caller's own reaction, it demands the exact emoji shortcode, and it requires user authorization. It stops short of saying whether the deletion is reversible or what happens on a missing reaction.

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 with the WRITE marker front-loaded so the mutation nature is visible at a glance. Every clause carries information: operation, ownership constraint, format requirement, auth prerequisite.

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?

With annotations covering safety and an output schema present, the description supplies the remaining essentials: authorization requirement, ownership restriction, and input format. Only edge-case behavior (nonexistent reaction, idempotency under retry) is unaddressed, which is minor for a narrow three-parameter tool.

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 parameter meaning; it does add format guidance for 'emoji' ('exact emoji shortcode', implying the :name: syntax the pattern enforces) and frames 'commentId' as an 'explicit' comment. The 'file' parameter gets no explanation at all, leaving one of three required params undocumented in prose.

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 (remove), a specific resource (a reaction), and the ownership scope (only the authenticated user's own reaction) on 'an explicit Figma comment'. That scope wording distinguishes it from both figma_add_reaction and figma_delete_comment without needing the sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'only the authenticated user's' phrasing implicitly excludes removing other users' reactions, which is the key usage boundary against figma_delete_comment or figma_delete_comments. However, it never explicitly states when to choose this over those siblings, nor what to do if the reaction is absent, so the routing is left to inference.

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