Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Rename a page or change its URL

rename_page

Rename a page (new_name) and/or move its URL (new_slug). Supply either or both — omitting new_slug derives it from the new name. Every internal link across the site is rewritten to the new URL, the navigation is re-synced, and link TEXT naming the old page is updated too, so this is the ONLY safe way to move a page: editing the file's name through update_variation_file leaves every link pointing at a URL that no longer exists. The homepage's URL cannot be changed. The page's content survives the move — its content namespace is deliberately not recomputed. Publish the site for the change to reach visitors; until then the live site keeps the old URL.

Input Schema

NameRequiredDescriptionDefault
slugYesCurrent slug of the page, e.g. "/services"
site_idYesThe site the page belongs to
new_nameNoNew display name, e.g. "Our Services". The stored file identifier is derived from it.
new_slugNoNew URL path, e.g. "/what-we-do". Derived from new_name when omitted. The homepage URL cannot be changed.
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_idNoDesign to edit, 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.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing site-wide consequences: every internal link is rewritten, navigation is re-synced, and link TEXT is updated. It also states that page content survives because the content namespace is not recomputed, and that the live site keeps the old URL until publish. Nothing contradicts destructiveHint=false — the operation is a coordinated rewrite, not a deletion.

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?

Front-loads what the tool does before the consequences, then the constraint, then the publish caveat. Dense but every sentence carries operational value; 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?

For a non-idempotent, open-world mutation with no output schema, the description supplies the missing pieces an agent needs: side effects, immutability constraint, content preservation, and the publish step to make it live.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is already documented. The description adds combination semantics not obvious from the schema — supply new_name, new_slug, or both, and omitting new_slug derives it from the new name — plus the constraint that the homepage URL is immutable. It does not explain variation_id or user_goal, but those are already self-documented.

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 / move its URL) and immediately ties it to the two parameters that control it. It explicitly names the sibling update_variation_file as the wrong way to move a page, so an agent can distinguish it without opening schemas.

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?

Gives explicit when-to-use (moving/renaming a page), when-not (editing a file name via update_variation_file), and a hard exclusion (the homepage's URL cannot be changed). It also states the precondition for the change to become visible: publish the site.

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