Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_get_comment_thread

Read-onlyIdempotent

Read a root Figma comment and its chronological replies; a reply ID resolves to its root thread. Use it to review full discussion context before replying or resolving feedback.

Instructions

Read a root comment and its chronological replies. A reply ID is resolved to its root thread.

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

Input Schema

NameRequiredDescriptionDefault
fileYes
commentIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
rootYes
fileKeyYes
repliesYes
resolvedYes
replyCountYes
resolvedAtYes
repliesIncludedYes

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add behavior beyond that. It does add two useful facts: replies are returned chronologically, and a reply ID is silently resolved up to its root thread rather than failing or returning just the reply. It stops short of mentioning permissions or pagination on long threads.

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, no filler, and the core action is front-loaded ahead of the clarifying ID-resolution note. Nothing could be removed without losing information.

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 two-parameter read tool with an output schema already documenting return values, this is nearly sufficient. The only material gap is the undefined 'file' identifier format, which an agent needs in order to call the tool successfully.

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 successfully clarifies that commentId accepts either a root or reply ID, which the bare 'string, minLength 1' schema does not convey. However, the 'file' parameter is left completely undefined — no indication whether it expects a file key, URL, or node ID.

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 uses a specific verb and resource ('Read a root comment and its chronological replies') and the second sentence clarifies the ID-resolution behavior. It implicitly distinguishes itself from figma_list_comments by operating on a single thread rather than enumerating comments, though it never names a sibling explicitly.

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?

Usage is only implied: the 'reply ID is resolved to its root thread' note suggests this is the tool to reach for when you have any comment ID, reply or root. There is no explicit statement of when to prefer this over figma_list_comments or when not to use it, so the agent must infer the boundary.

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