Skip to main content
Glama
the-real-talk

the-real-talk

delete_page

Deletes a Figma page by ID while refusing the active page and the only remaining page.

Instructions

Delete a page (by ID). Refuses the active page and the only page.

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": "delete_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 behavioral burden. It usefully discloses two guardrails (active page, sole page), but it never states that deletion is permanent/irreversible, what happens to child nodes or components on the page, or any permission requirement.

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 terse sentences, guardrail front-loaded immediately after the action, with zero redundant wording.

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 destructive, annotation-free mutation, the definition covers the minimum (action, target, refusal conditions) but omits irreversibility, side effects on page contents, and error behavior—meaningful gaps for a delete operation.

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 coverage is 0% with a single required string parameter. '(by ID)' is the only semantic hint and it merely classifies pageId as an identifier; it does not say where to obtain the ID or whether names are accepted, so the coverage gap is only partly offset.

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 names a specific verb and resource ('Delete a page') and scopes it to an ID-based target, which cleanly separates it from create_page/rename_page. It stops short of an explicit contrast with siblings, but the purpose is unambiguous.

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?

'Refuses the active page and the only page' tells the agent the two conditions under which the call is rejected, which is real when-not guidance. It does not say what to do instead (e.g., switch the current page first), so it is not a full 5.

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