Skip to main content
Glama
processedfood

figma-comments-mcp

Get recent comments

get_recent_comments

Retrieve comment threads from a Figma file that have been active within the specified time window. Supports filtering by page, author, or keyword.

Instructions

Comment threads with activity in the past N hours (default 24).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA figma.com file link (design/file URL) or a bare file key
pageNoOptional: limit to one page, by page name (e.g. "Homepage") or page id (e.g. "1:2" or "1-2")
authorNoOptional: only threads where this person wrote a message. Matches the Figma handle, partial and case-insensitive.
searchNoOptional: only threads whose text contains this keyword (case-insensitive)
max_threadsNoCap on unresolved threads shown, newest first (default 50)
hoursNoLook-back window in hours, default 24
Behavior2/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It only mentions the time filter and default, but omits ordering (likely newest first), pagination, or limits beyond max_threads. The return format is unspecified.

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?

The description is a single concise sentence that immediately conveys the core purpose. It is front-loaded and avoids unnecessary words.

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?

Given the low complexity (no nested objects, no output schema), the description is somewhat complete for a basic time-filtered query. However, it lacks details on what constitutes 'activity' and the response structure, which would be helpful for an AI agent.

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 100%, so the baseline is 3. The description adds minimal value beyond the schema (e.g., reiterates default 24). It does not clarify parameter relationships or elaborate on optional parameters.

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 clearly states the tool retrieves comment threads filtered by time since last activity, with a default of 24 hours. This distinguishes it from sibling tools like get_all_comments (no time filter) and get_unresolved_comments (status filter).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies use for recent activity but does not mention exclusions or comparisons to sibling tools like get_comments_mentioning_me or get_all_comments.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/processedfood/figma-comments-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server