Skip to main content
Glama

maket_doc

Manage design documents: create, duplicate, rename, delete, list, update metadata, and export/import portable .maket bundles.

Instructions

When to use: every persistent document-lifecycle operation — create, clone, rename, delete, list, update metadata, or move bundles in/out. For session-level actions (open a doc/page in the preview, inspect state, lock), use maket_workspace. For per-page edits use maket_page and for content use maket_html.

doc is the doc in scope for every action except list. name only appears when you need a NEW name (duplicate, rename).

Manage design documents (the workspace unit: canvas + pages + meta). new — create a blank document at doc; sets it active. Previous unsaved work is lost. list — enumerate saved documents grouped by category. delete — remove doc permanently; refused if it's the only document left. duplicate — clone docname (format variants, A/B copies). rename — rename docname. meta — update doc's metadata: designNotes, teamNotes, rating, category, charte. export — write a portable .maket bundle to EXPORTS_DIR. By default the bundle embeds referenced asset binaries (images, SVGs) so it survives transfer to another machine or a fresh datadir. Pass include_assets=false for a lighter structure-only snapshot. Include doc for a single document, docs for a list, or omit both to export every document. Referenced chartes are embedded automatically. Override the filename with output. import — load a .maket bundle from input (absolute path or EXPORTS_DIR-relative). Documents land with conflict-renamed names; chartes skip names that already exist so your current brand isn't overwritten. Assets in the bundle are restored to ASSETS_DIR with the same collision-renaming rule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docNoThe doc in scope. Required for every action except list. For new: the new doc's name (must be unique). For delete/meta: the doc to act on. For duplicate/rename: the source doc.
docsNoFor export: list of doc names to include in the bundle. Omit to export all documents. Ignored by other actions.
nameNoThe new name. Only used by duplicate (clone's name) and rename (new name).
inputNoFor import: absolute or EXPORTS_DIR-relative path to a .maket file to load.
actionYesOperation to run. See the tool description for the action table.
charteNoFor new/meta: name of an existing charte to associate with this document. The charte itself is applied later via maket_charte view.
formatNoFor new: paper/screen format. Default A3. Paper sizes are mm; DESKTOP/TABLET/MOBILE are screen aspect ratios scaled to mm.
outputNoFor export: output filename (defaults to <doc>.maket or maket-bundle.maket). Absolute paths are honoured; bare names land in EXPORTS_DIR.
ratingNoFor meta: 0–5 star rating (clamped).
marginsNoFor new: per-side safe-zone insets in mm {top, right, bottom, left}. Optional.
categoryNoFor new/meta: category tag used for grouping in list (default general).
teamNotesNoFor meta: team-facing notes (visible in the UI).
backgroundNoFor new: canvas background colour (CSS). Default #ffffff.
designNotesNoFor meta: designer-facing notes (visible in the UI).
orientationNoFor new: page orientation. Default portrait.
include_assetsNoFor export: embed referenced asset binaries (images, SVGs) in the bundle. Default true — produces a portable .maket that survives transfer to another machine or datadir. Set false for a structure-only snapshot (smaller, git-friendly).
Behavior5/5

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

Discloses important behaviors beyond the action list: 'new' causes previous unsaved work to be lost, 'delete' is refused if only document left, import uses conflict-renaming and skips existing chartes, export embeds asset binaries by default. No annotations provided, so description carries full burden and meets it excellently.

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?

Description is well-structured with an action table and clear parameter notes, but is somewhat lengthy. Could be slightly more concise without losing clarity, but it is front-loaded with the most important usage guidance.

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?

Given the tool's complexity (16 parameters, 8 actions, no output schema), the description covers all actions, edge cases (only document left, conflict renaming), and parameter usage comprehensively. No gaps identified.

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

Parameters5/5

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

Schema has 100% coverage, but the description adds value by explaining which actions use each parameter (e.g., 'name only appears when you need a NEW name') and clarifying the role of 'doc' as the scope. Also explains export parameters (include_assets, output) with detailed context.

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 clearly states it manages design documents (canvas + pages + meta) and lists all lifecycle operations (create, clone, rename, delete, list, update metadata, move bundles). It explicitly distinguishes from siblings: maket_workspace for session-level actions, maket_page for per-page edits, maket_html for content.

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?

Provides explicit when to use ('every persistent document-lifecycle operation') and when not to (session-level -> workspace, per-page edits -> page, content -> html). Also notes that 'doc' is required for all actions except list, and 'name' only for duplicate/rename.

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