Skip to main content
Glama

figma_get_current_page

Retrieves the current page summary, top-level child nodes, and selection from the open Figma file so you can inspect and act on page content.

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_current_page"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Get' implies a read-only, side-effect-free operation, and the enumeration of returned content (page summary, top-level children, selection) provides useful disclosure of the output. It says nothing about scope limits, permission requirements, or whether the selection may be empty, so it is adequate but incomplete.

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?

A single sentence with no wasted words, and the three outputs are listed directly rather than buried behind preamble. It is appropriately sized, though the brevity means it also lacks any structural grouping or ordering cues for the returned content.

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, the description must convey return values, and it does list three of them. However, for a context-dependent Figma tool, it omits how the current page is determined and what happens when nothing is selected, leaving gaps an agent would want filled.

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 the baseline is 4. There is nothing parameter-wise for the description to add, and it correctly makes no parameter claims.

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 (获取/get) plus a clear resource (当前页/current page), and enumerates the three things returned: page summary, top-level child nodes, and selection. An agent knows what it does without opening a schema. It does not name or distinguish itself from the overlapping siblings figma_get_selection or figma_get_document_info, so it stops short of a 5.

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?

It gives no when-to-use guidance, no prerequisites (such as an open document or an active page), and no indication of when to prefer this over figma_get_selection or figma_get_document_info. At best, the usage is implied by the listed return contents, which leaves the agent to infer the context.

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