Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_set_page

Switches the Figma editor to a specified page by name without modifying the document, so agents can work on the correct page.

Instructions

Switch the Figma editor to another page. Editor state only; the document is not modified.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact page name
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the most important trait — the change is editor state only and the document is not modified — which tells an agent this is non-destructive and non-persistent. It omits failure behavior (nonexistent page name), whether pages can be created, and any permission or connection prerequisites beyond what the schema states.

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?

Two tight sentences with the action front-loaded and the scope caveat immediately after. Nothing is wasted, though the second sentence could carry slightly more operational detail at no length cost.

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

Completeness4/5

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

For a simple two-parameter tool with full schema coverage and no output schema, the description covers purpose and the key non-destructiveness fact. Only error/edge behavior for an invalid page name is left unaddressed.

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 both 'name' and 'fileKey' are already documented in the schema, including the multi-file fallback rule. The description adds no meaning beyond that, so the baseline of 3 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?

States a specific verb and object ('Switch the Figma editor to another page') and immediately scopes it as editor state rather than a document mutation. That scope note separates it from document-mutating siblings such as figma_batch_edit, though no sibling is named explicitly.

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 implied: call this when you want a different page active in the editor. There is no explicit when-not guidance, no mention of what happens with an unknown page name, and no routing to an alternative tool for other page-related operations.

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