Skip to main content
Glama

figma_get_selection

Retrieves a summary of the current Figma selection, returning an empty array when nothing is selected.

Instructions

获取当前选区摘要。空选区返回空数组,不是错误。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "figma_get_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose one genuinely valuable behavioral fact — an empty selection yields an empty array rather than an error — which prevents an agent from misreading the result as a failure. However, it says nothing about whether the call requires Figma to be open, whether it is read-only, or what fields the summary contains.

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 clauses, zero waste, with the primary purpose stated first and the edge case second. Nothing redundant and nothing likely to be skimmed past.

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 no output schema and no annotations, the description is the only source of truth about the return value, yet it only says the result is an 'array' in the empty case and never describes what a non-empty summary contains (node ids, names, types, counts). For a zero-param read tool this is adequate to call correctly but incomplete for interpreting the response.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to elaborate; the baseline for a parameterless tool applies.

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?

"获取当前选区摘要" names a specific verb (get) and resource (current selection summary), which an agent can distinguish from read siblings like figma_get_document_info or figma_get_node. It stops short of explicitly contrasting itself with those siblings, but the scope is unambiguous.

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 by the object of the verb: an agent should call this when it needs to know what the user currently has selected. There is no explicit when-to-use condition, no mention of when another tool (e.g. figma_get_node with an id) would be preferable, and no prerequisites.

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