Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

List page drafts

list_page_drafts
Read-onlyIdempotent

List the drafts of a page — private copies someone is trying out before making them live — or, with no page_slug, every page in the design that has drafts. Each draft comes back with its slug (what update_variation_file / refine_site target), its name, the live page_slug it belongs to, and its content_key (the draft's own text, for patch_variation_content). design.variation_index is the index to pass to those edit tools. Read-only.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site to read
page_slugNoOnly this page's drafts, e.g. "/about" or "/" for the home page. Omit to list every page that has drafts.
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 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.4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, so the description does not need to carry the safety profile. It adds useful context by explaining what each returned field is for and how `design.variation_index` connects to the edit tools. Pagination and result-size behavior are not described, which keeps it from a 5.

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?

The description is front-loaded, dense, and every clause contributes either scope, return-field meaning, or tool routing. The long first sentence carries several parenthetical mappings, but it remains readable and avoids 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?

There is no output schema, so the description appropriately explains the shape of returned draft records and how their fields are used by edit tools. Combined with 100% schema coverage and annotations covering safety, it gives an agent enough information to call the tool correctly and use the results.

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 the parameter baseline is 3, but the description adds value by explaining the practical meaning of `page_slug` omission and how returned values such as `slug`, `content_key`, and `design.variation_index` should be used downstream. It does not add syntax details beyond the schema, but the field-to-tool mapping is meaningful.

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 uses a specific verb and resource: it lists page drafts and explains that drafts are private copies being tried out before going live. It also distinguishes both call modes, per-page and all pages with drafts, so an agent can tell exactly what this tool returns.

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?

It clearly states the scoping behavior when `page_slug` is omitted and maps returned fields to the edit tools that consume them (`update_variation_file`, `refine_site`, `patch_variation_content`). It does not explicitly name when to use this instead of nearby list tools such as `list_content_drafts` or `list_variations`, but the intended workflow is easy to infer.

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