own.page

Delete a subpage

delete_page

Destructive

Delete a subpage for good, with all its widgets. The home page can't be deleted. This can NOT be undone: always ask the user to confirm first, then call with confirm: true.

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": {
      "page": "<page>",
      "confirm": "<confirm>"
    },
    "name": "delete_page"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes	Slug of the subpage to delete (from list_pages).
`confirm`	Yes	Must be true, after the user confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes further by disclosing the cascade effect (all widgets go with it), the irreversibility constraint, and the user-confirmation requirement. These are exactly the operational facts an agent needs before invoking a destructive tool.

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?

Three short sentences, front-loaded with the destructive consequence, then the exclusion, then the required procedure. No filler and nothing redundant.

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

Completeness5/5

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

For a two-parameter destructive tool with no output schema, the definition covers impact, exclusions, irreversibility, and preconditions. Nothing an agent needs in order to call this safely is missing.

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 100% and both parameters are documented inline, so the schema already carries the parameter meaning including the confirm gating semantics. The description reinforces the required ordering (ask first, then confirm: true) but adds no format or sourcing detail beyond the schema's reference to list_pages.

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 names a specific verb and resource ("Delete a subpage") and adds scope detail absent from the name: it removes the page's widgets along with it. It is clearly distinguishable from the widget-level siblings like remove_widget and from non-destructive page tools like rename_page.

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

Usage Guidelines5/5

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

It states a hard exclusion ("The home page can't be deleted") and a mandatory precondition workflow (ask the user to confirm, then call with confirm: true). An agent knows both when it may call this and what sequence it must follow before calling.

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

All own.page tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?