Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_reply_to_comment

Publishes a reply in an existing Figma comment thread using the root comment ID, enabling direct responses within the correct discussion.

Instructions

WRITE: publish a reply into an existing Figma thread as the authenticated user. Supply the root comment ID, not a reply ID. Requires user authorization to communicate.

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>",
      "message": "<message>"
    },
    "name": "figma_reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
messageYes
commentIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
authorYes
rootIdYes
messageYes
orderIdYes
parentIdYes
createdAtYes
reactionsYes
clientMetaYes
resolvedAtYes
reactionsKnownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the mutation profile is covered. The description adds non-obvious context annotations do not carry: the reply is published as the authenticated user and requires user authorization to communicate. It omits anything about failure modes or whether retries could duplicate a reply, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with a 'WRITE:' marker that signals side effects immediately. No filler; each clause carries information, though the phrasing is telegraphic rather than smoothly structured.

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?

With an output schema present, return values need not be explained, and the auth requirement is stated. Still, for a non-idempotent open-world write, the definition leaves the 'file' parameter ambiguous and gives no sense of what happens on an invalid or already-resolved thread.

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?

Schema description coverage is 0%, so the description bears the full burden for three required parameters. It meaningfully constrains commentId (root comment ID, not a reply ID) but says nothing about 'file' (is it a file key, a URL, a node ID?) or 'message' (length limits, plain text vs markdown). One of three parameters is clarified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with an explicit verb+resource pair, 'publish a reply into an existing Figma thread,' and scopes it to the authenticated user. It is clearly distinct from a generic comment-posting action by insisting on an *existing* thread, though it never names the sibling it differs from (e.g. figma_post_comment).

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?

'Supply the root comment ID, not a reply ID' is a genuine usage constraint that prevents a common calling mistake, and 'existing Figma thread' implies the when-to-use context. However, no alternative tool is named and there is no explicit when-not-to-use guidance versus figma_post_comment or figma_get_comment_thread.

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