Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Delete a page

delete_page
Destructive

Delete ONE page from a site's design. Links to it are removed from the other pages and it leaves the navigation. It goes to the site's trash and is recorded in version history, so it can be restored. The home page cannot be deleted. Publish for visitors to stop seeing it.

Input Schema

NameRequiredDescriptionDefault
slugYesThe page's slug, e.g. "/about" (get_site lists them). The home page cannot be deleted.
site_idYesThe site to act on
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
variation_idNoThe design to change. Omit for the site's live design.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=false, but the description adds substantial context: links to the page are stripped from other pages, it leaves navigation, it moves to trash, it is recorded in version history and restorable, and the home page is protected. That is exactly the behavioral detail an agent needs for a destructive call.

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?

Front-loaded with the action and scope, then side effects, then constraints. Every sentence is useful, though the trailing 'Publish for visitors to stop seeing it' is a slightly disconnected follow-up instruction.

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 destructive, four-parameter tool with no output schema, the description covers what is removed, where it goes, recoverability, and the one blocked case. Nothing material is missing for correct invocation.

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 slug, site_id, variation_id and user_goal are already documented. The description only echoes the slug's home-page constraint already stated in the schema, adding no new parameter meaning — baseline 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?

States a specific verb and resource with explicit scope ('Delete ONE page from a site's design'), which distinguishes it from bulk/page-draft siblings like delete_page_draft or delete_submissions. An agent immediately knows the operation and its granularity.

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?

Gives clear conditions: the home page cannot be deleted, and publishing is what makes the removal visible to visitors. It does not explicitly route to an alternative (e.g. delete_page_draft for drafts), so it stops short of full when/when-not guidance.

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

All Mondovo toolsInspect
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