Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Delete a page draft

delete_page_draft
Destructive

Delete a page draft and its copy of the text. The live page is not touched. Recorded in version history, so restore_version can bring it back. Confirm with the user before deleting a draft they made. page_slug is optional — it is worked out from the draft.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site the draft belongs to
page_slugNoThe live page the draft belongs to. Optional — worked out from the draft when omitted.
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.
draft_slugYesThe draft's slug, from create_page_draft or list_page_drafts (e.g. "/about--draft-7f2a").
variation_idNoDesign the draft belongs to, from list_variations. Defaults to the active 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.5/5.0
Behavior5/5

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

Annotations say destructive/non-idempotent, but the description adds what actually gets destroyed (draft plus its text copy, not the live page), that the deletion is recorded in version history and reversible via restore_version, and that user confirmation is expected. That is genuine value beyond the annotation flags.

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?

Four short sentences, each carrying a distinct fact: what is deleted, what is not, reversibility, and confirmation etiquette. Front-loaded with the destructive scope, no filler.

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?

With no output schema and full schema description coverage, the description supplies exactly the missing behavioral layer — destruction scope, reversibility, recovery tool, and confirmation policy — leaving nothing an agent needs before calling it.

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%, so all five parameters are already documented, including that page_slug is optional and derived from the draft. The description's note about page_slug repeats the schema rather than adding syntax or constraints; 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?

Specific verb+resource (delete a page draft) plus explicit scope: it removes the draft and 'its copy of the text', while 'the live page is not touched'. That scope statement distinguishes it cleanly from delete_page and delete_function.

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 a concrete when-not/alternative: the live page is unaffected (use delete_page for that), and recovery goes through restore_version. Adds a confirmation instruction for drafts the user authored. No explicit guidance on when to prefer rename/promote over delete, but the core routing is clear.

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