Skip to main content
Glama
arimunandar

figsnap-mcp

by arimunandar

Curate the saved set

figma_saved

Manage a designer's shortlist of Figma nodes by saving, listing, moving, or removing bookmarks, grouped into folders—without altering the design itself.

Instructions

Read and change the designer’s shortlist of nodes in this file, and the folders it is grouped into. One action argument: list, folders, save, unsave, clear, move, newFolder, renameFolder, deleteFolder.

list — the entries, optionally in one folder. folders — the folders with their counts; "" is the root. save — add nodeIds, or whatever is selected when you give none. unsave — remove nodeIds. clear — empty one folder, or the whole set when you name none. move — put nodeIds in folder. newFolder / renameFolder / deleteFolder — the folders themselves; deleteFolder keeps the entries and returns them to the root unless deleteEntries is true.

This is a bookmark list, not the design: it lives in the plugin’s own storage, so none of it is behind the Edits switch and none of it can be undone with Cmd-Z. Saving what a long job is about is a cheap way to leave the designer something to look at afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoFor renameFolder: what to call it instead.
fromNoFor renameFolder: the folder as it is called now.
nameNoFor newFolder and deleteFolder.
actionYesWhich of the nine.
folderNoFor list, save, clear and move. "" is the root; the folder must already exist for move.
nodeIdsNoFor save, unsave and move. Omitting them on save means the current selection.
deleteEntriesNoFor deleteFolder: remove what was in it too, rather than returning it to the root.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses important non-obvious behavior beyond the annotations: changes live in plugin storage, are not behind the Edits switch, cannot be undone with Cmd-Z, and deleteFolder returns entries to root by default unless deleteEntries is true. This is rich, accurate behavioral context with no contradiction against the annotations.

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?

The description is long but appropriately so for nine distinct actions. It front-loads the overall purpose, then uses a compact action-by-action list, and each sentence carries operational meaning. The closing rationale, while not strictly necessary, reinforces the intended use without bloating the definition.

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

Completeness5/5

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

For a multi-action tool with no output schema, this description is exceptionally complete: it covers every action, all parameter scoping rules, defaults, special cases, and persistence semantics. An agent has enough to call the tool correctly across all nine actions.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds action-level semantics that the schema alone does not fully convey: omitting nodeIds on save means current selection, "" means root, and deleteFolder's default non-destructive behavior. These details help an agent bind parameters correctly per action.

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 opens with a specific verb-resource pair: 'Read and change the designer’s shortlist of nodes in this file, and the folders it is grouped into.' It then enumerates all nine actions, making the scope unmistakable and distinguishing this curation tool from read-only siblings like figma_list_saved.

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

Usage Guidelines4/5

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

The description gives clear context for when this tool is appropriate: it manages a persistent bookmark list separate from the design, and the closing sentence provides a concrete use case. It does not explicitly name sibling alternatives or say when not to use it, so it stops short of a 5.

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

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/arimunandar/figsnap-mcp'

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