Skip to main content
Glama

Pages and references

pages
Destructive

Add, update, remove, reorder, clone, or set page locks and manage reference images. A book holds up to 100 pages. One add accepts up to 50 coloring pages, plus an optional front cover and back cover. startGeneration queues the pages just added and requires confirmToken from a generate quote in append mode for those pages and covers. clone copies one coloring page, including an uploaded image, onto a new object key. Cover pages cannot be cloned, pages with generation in progress cannot be cloned, and clone refuses when the book is already full. set_page_locks toggles locked on one or more page ids (locked pages skip batch regenerate and block prompt edits, image replace, and page reference changes until unlocked). upload_image and add_refs accept imageUrl or base64. add_refs, remove_ref, and reorder_refs take an optional pageId; when set they edit that page's reference images (max 3), and book images are sent before page images. Image generation spends the website token balance. Purchases happen at /pricing; this tool never takes payment.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive and non-read-only annotations, the description discloses key behavior: a book holds up to 100 pages, one add accepts up to 50 pages plus covers, clone copies uploaded images and has refusal conditions, locks affect regenerate and edits, and image generation spends the token balance. It also clarifies that the tool never takes payment and points purchases to /pricing.

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 dense but front-loaded, starting with the full operation set before moving into constraints and side effects. It is appropriately sized for a ten-operation tool, though it would be easier to scan if grouped by operation rather than packed into one paragraph.

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 complex multi-operation tool with no output schema, the description covers the major invocation constraints, side effects, limits, and cross-operation dependencies. The main remaining gap is that it does not describe return values or what identifiers are produced by add, clone, or upload operations, which can matter for chaining calls.

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?

Although schema coverage is high, the description adds cross-parameter meaning that the schema alone does not make obvious: confirmToken must come from a generate quote in append mode, optional pageId on ref operations switches between page-level and book-level reference images, and add_refs supports at most 3 page references. It does not explain every field such as locale, title, status, role, or order, but it substantially clarifies the operationally important parameters.

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 opens with a specific verb-and-resource list: add, update, remove, reorder, clone, set page locks, and manage reference images. It makes clear this is page-level book management rather than book-level operations, and later names individual ops like startGeneration, upload_image, add_refs, remove_ref, and reorder_refs.

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 gives meaningful usage conditions: startGeneration requires a confirmToken from a generate quote in append mode, clone is refused for covers, in-progress pages, or full books, and locked pages block prompt edits, image replacement, and reference changes. It does not explicitly say when to use this tool instead of siblings such as books or generate, so it falls short of fully explicit alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources