Skip to main content
Glama

delete_page

Destructive

Remove a page from a Figma document using its ID or name. Prevents deletion of the last remaining page.

Instructions

Delete a page from the Figma document. Cannot delete the only remaining page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdNoPage node ID in colon format e.g. '0:2'
pageNameNoExact page name to delete (alternative to pageId)
Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description adds the critical behavior that it cannot delete the only remaining page. No contradictions.

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 sentences, front-loaded with the primary action, and the second sentence adds a crucial constraint with no wasted words.

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 destructive tool with two optional parameters and no output schema, the description covers the essential purpose and a key safety constraint. Could mention behavior when no parameters provided, but sufficient overall.

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?

Input schema coverage is 100% with both parameters already described in schema. The description does not add any additional meaning beyond what the schema provides, so a baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Delete a page from the Figma document', using a specific verb and resource. It distinguishes from other deletion tools like delete_nodes by targeting pages specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Cannot delete the only remaining page', providing a key constraint. It does not mention alternatives or when not to use, but the constraint is valuable guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vkhanhqui/figma-mcp-go'

If you have feedback or need assistance with the MCP directory API, please join our Discord server