Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Rename a page draft

rename_page_draft
Idempotent

Rename a page draft (the label the user sees in the editor's drafts bar). Changes nothing else. page_slug is optional — it is worked out from the draft.

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name, 1–60 characters.
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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful scope information: it changes nothing else besides the draft label, and page_slug is auto-derived when omitted. It does not discuss permissions or side effects further, but the annotations cover the safety profile.

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 short sentences, front-loaded with the action and scope, followed by the only non-obvious parameter behavior. Every clause is useful and there is no filler.

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 idempotent rename mutation with full schema descriptions and no output schema, the description supplies the key scope and optional-parameter context. It could explicitly contrast with rename_page, but the core information needed to call it correctly is present.

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 all six parameters are already documented in the schema. The description mentions page_slug being optional and derived from the draft, but this only restates what the schema already says and adds no new syntax or constraint details.

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 ("Rename a page draft") and immediately scopes it to the label shown in the editor's drafts bar. That distinguishes it from rename_page and the other rename_* siblings without needing to name them explicitly.

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 gives clear context for when this tool applies: renaming only the draft label, not the live page, and notes that page_slug is optional. It does not explicitly say to use rename_page for the live page, but the draft-vs-page distinction is sufficiently 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