Skip to main content
Glama

maket_page

Manage page structure within documents: add, remove, rename, reorder, or list pages. For page content, use the dedicated HTML tool.

Instructions

When to use: manage page structure within a document — add, remove, rename, reorder, list. For page content, use maket_html instead.

Manage pages within a document (structure only, not content). add — append a new page with initial HTML; sets it active. remove — delete a page by 1-based index or name; refused if it's the last page. rename — rename a page by index or current name. reorder — move a page from one 1-based position to another; activePage adjusts. list — list pages with element counts; the active page is marked ●.

Note: charte compliance (token-literal colours, font-family, box-shadow) is enforced by maket_html set/patch, not by maket_page add. If the new page must match a charte, follow maket_page add with maket_html set to validate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoFor reorder: target 1-based position.
docYesDocument name (always required).
fromNoFor reorder: source 1-based position.
htmlNoFor add: HTML body for the new page. Relative image src values are normalized to /assets/...
nameNoFor add/rename: page name (new page name, or rename target).
pageNoFor remove/rename: target page — either 1-based index or page name.
actionYesOperation to run. See the tool description for the action table.
Behavior4/5

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

No annotations, but description details behavior per action (active page on add, rejection of removal of last page, activePage adjustment on reorder, marking active page on list). Could note destructive nature of remove more explicitly.

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?

Well-structured with headings and bullet points. Every sentence adds information. No redundant text.

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?

Given no output schema and no annotations, description covers all actions and parameters comprehensively. Return format for list is implied but not explicit. Note on charte compliance is helpful.

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 100% provides parameter descriptions, but the description adds value by grouping parameters per action and explaining their purpose in context (e.g., 'For add: HTML body for the new page').

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?

Description states 'manage page structure within a document — add, remove, rename, reorder, list.' Clearly distinguishes from sibling 'maket_html' for content. Specific verb and resource.

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?

Explicit 'When to use' and contrast with maket_html. Provides clear context for each action. Includes note on charte compliance sequencing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ng-galien/maket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server