Skip to main content
Glama

maket_doc

Manage design documents across their lifecycle: create, list, duplicate, rename, delete, update metadata, and export or 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 as a hierarchy of category paths. 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, collections, and current document-state snapshots are embedded automatically; revision history stays local. 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 and collections skip names that already exist. Current document-state snapshots initialize revision 1, and assets are restored to ASSETS_DIR with the existing collision 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 path separated by / (for example clients/acme). Flat values remain valid roots; 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?

With no annotations, the description carries the full burden of behavioral disclosure and does so thoroughly. It discloses side effects: 'new... sets it active. Previous unsaved work is lost'; deletion 'refused if it's the only document left'; export embeds assets by default and import renaming/conflict behavior; revision history stays local; current state snapshots initialize revision 1. This is rich, honest, and prevents misuse.

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 long, but appropriately so for an 8-action tool with 16 parameters. It is front-loaded with a 'When to use' paragraph, and the action table is structured with bold names and bullet-like details. No filler sentences; every line conveys operational information. It could be slightly tightened, but it earns the length.

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?

This is a complex, multi-action tool with no output schema and no annotations. The description covers every action's purpose, parameter constraints, defaults, side effects, and edge cases (e.g., single-document deletion refusal, export portability, import conflict resolution). It provides sufficient context for an agent to invoke any action correctly without referring to external documentation.

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 baseline is 3. The description adds value beyond the schema with a concise rule: 'doc is the doc in scope for every action except list. name only appears when you need a NEW name.' It also summarizes export/import parameter semantics (include_assets, docs, output, input) and clarifies action-parameter relationships. This elevates it slightly above baseline.

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 the tool's purpose: 'Manage design documents (the workspace unit: canvas + pages + meta)' and enumerates all actions (new, list, delete, duplicate, rename, meta, export, import). The opening 'When to use' paragraph explicitly distinguishes it from sibling tools (maket_workspace, maket_page, maket_html), making its scope unambiguous.

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?

The description opens with explicit guidance: 'When to use: every persistent document-lifecycle operation...' and names alternatives for session-level actions, per-page edits, and content. It also provides per-action details, such as which parameters apply to which action, giving the agent clear decision rules.

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