Skip to main content
Glama
Figma Comments MCP

Figma Comments MCP

by RussGallaway

figma_post_comment

Publish a new top-level Figma comment as the authenticated user; optionally pin it to a canvas position or node for precise feedback.

Instructions

WRITE: publish a new top-level Figma comment as the authenticated user. Optional valid canvas or node positioning pins the comment. 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>",
      "message": "<message>"
    },
    "name": "figma_post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
messageYes
clientMetaNo

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write/safety profile is covered. The description adds non-trivial context beyond that: the comment is published as the authenticated user, requires user authorization to communicate, and positioning is optional, which explains mutation and auth requirements the annotations do not.

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 with the operation type front-loaded as 'WRITE:' and zero redundant phrasing. The lone weak spot is the vague word 'valid', which spends a sentence's worth of attention on an undefined constraint.

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?

An output schema exists, so return values need not be explained, and the definition covers mutation, actor identity, authorization and optional positioning. It falls short on what happens with the region/pin-corner variants of clientMeta and on any error or duplicate-comment behavior.

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 compensate for all three parameters, and it only partially does: 'canvas or node positioning pins the comment' conveys the two clientMeta modes. It adds nothing about 'file' or 'message', and the qualifier 'valid' is undefined, so the region and pin-corner variants of clientMeta remain 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?

The description states a specific verb and resource ('publish a new top-level Figma comment') and pins down the actor ('as the authenticated user'). The word 'top-level' distinguishes it from figma_reply_to_comment without needing the sibling's schema.

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 implied by 'top-level' and by the authorization prerequisite, but the description never explicitly routes the agent to figma_reply_to_comment for replies or to figma_list_comments for reading. Adequate but leaves the alternative-selection step to inference.

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