Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_add_reaction

Adds the authenticated user's emoji reaction to a specified Figma comment using a supported shortcode such as :heart:, requiring authorization.

Instructions

WRITE: add the authenticated user's reaction to an explicit Figma comment. Supply a Figma-supported emoji shortcode, such as :heart:. 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_add_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

A3.8/5.0
Behavior4/5

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

Annotations already declare write, openWorld, non-idempotent, non-destructive, so the write nature is not new information. The description earns credit for two added facts not in the annotations: the operation acts on behalf of the authenticated user and requires user authorization. It stays silent on duplicate-reaction behavior, which the non-idempotent hint makes relevant.

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 short sentences, with the operation type front-loaded and the key constraint and prerequisite following immediately. No filler, no repetition of the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema and annotations lowers the descriptive burden, and the auth requirement plus emoji constraint cover the riskiest parts. However, for a three-required-parameter tool with zero schema coverage, leaving 'file' entirely unexplained is a real completeness gap an agent must guess around.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must carry parameter meaning, and it only partially does. It constrains the emoji to a Figma-supported shortcode with an example and implies commentId must reference an existing comment, but the required 'file' parameter is never mentioned and neither is the expected identifier format for commentId or file.

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?

"WRITE: add the authenticated user's reaction to an explicit Figma comment" names a specific verb and resource, scopes whose reaction it is, and makes clear the target must be an existing comment. This cleanly separates it from figma_delete_reaction and the comment-posting/reply siblings.

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 description implies when to use it (attaching a reaction to an existing comment) and states the prerequisite of user authorization, but it never names an alternative or states when not to use it, e.g. reacting to something that is not a comment or reacting as another user. Usage guidance is inferred rather than explicit.

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