Skip to main content
Glama
the-real-talk

the-real-talk

set_current_page

Sets a Figma page as the active page by ID so edits and queries target the intended design page.

Instructions

Make a page the active page (by ID).

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": {
      "pageId": "<pageId>"
    },
    "name": "set_current_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and falls well short. It implies a UI state change but does not say whether it is reversible, whether it errors on a nonexistent page, whether it alters the agent's viewport or selection, or how it interacts with collaborative editing state.

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 short sentence, front-loaded with the action and with zero filler. Its brevity is close to under-specification rather than verbosity, so it is efficient but thin.

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?

For a one-parameter, non-output tool this covers the core action and how the target is identified. It leaves the agent without enough information on failure modes or observable effects of switching the active page, which matters for a state-mutating tool with no annotations.

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 should compensate; it only adds "by ID", which merely restates the parameter name pageId. It does confirm the value is an identifier rather than a page name, which is useful, but nothing about format, source, or validation is added.

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?

States a specific verb ("make ... the active page") and resource (page), which is a distinct concept from the sibling operations create_page, delete_page and rename_page. An agent can tell this changes the current/active page rather than the page's content or existence, though the term "active page" is never explained.

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 indication of when to use this versus alternatives, no prerequisites (does the page need to already exist? is it scoped to the current document?), and no note about side effects on selection or viewport. The only guidance is the parenthetical "by ID", which addresses identification rather than usage context.

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

Deploy Server

Other Tools