Skip to main content
Glama
the-real-talk

the-real-talk

rename_page

Update a Figma page's name by providing its page ID and new label, so you can keep design files organized without manual edits.

Instructions

Rename a 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": "<name>"
    },
    "name": "rename_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation. It does not disclose permission requirements, whether renaming is idempotent, whether the old name is preserved anywhere, or what errors occur for an invalid pageId. Only the 'by ID' lookup hint adds anything beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words with zero padding and the lookup key front-loaded, so nothing is wasted. However, the extreme terseness reads as under-specification rather than economy for a two-parameter mutation tool.

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

Completeness2/5

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

A destructive-style rename operation with no annotations, no output schema, and no parameter documentation leaves the agent without permissions, return value, or failure-mode information. Relative to the complexity of a mutation on a document object, this is substantially incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, and the schema itself is degenerate: 'name' is a $ref to the pageId definition rather than a documented new-name field. The description only covers the pageId side of the call and never states that 'name' is the replacement page name or any constraints on it.

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 resource: rename a page, with the lookup key 'by ID' made explicit. It implicitly differentiates itself from rename_node and rename_variable by naming the resource type, though it never explicitly contrasts with those siblings.

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?

There is no guidance on when to use this versus alternatives such as rename_node or set_current_page, no prerequisites, and no note about what happens if the page ID doesn't exist. The agent must infer everything from the single sentence.

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