Tapercraft — VHS Label Maker

Export a print file

export_design

Render a saved design. Queues a job — a headless renderer produces the file in ~15–60 s — and returns a jobId; poll get_export. output 'preview' (every plan) is a downscaled image of the whole sheet that get_export returns INLINE so you can look at it: render one after every save, check the layout, cover art, text sizes and colours against what the user asked for, fix the intent and save again before exporting. 'png' is the Original full-resolution print PNG (600 DPI) and 'pdf' its design-size PDF — members only, and only once the preview looks right. Needs an API key with the export scope.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`output`	No	'preview' to see the design, 'png' (default) or 'pdf' for the print file
`designId`	Yes	From save_design or list_designs

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / output / description

Previous value: -"'png' (default) or 'pdf'"New value: +"'preview' to see the design, 'png' (default) or 'pdf' for the print file"

changedInput schema / properties / output / enum

Previous value: -[
-  "png",
-  "pdf"
-]New value: +[
+  "png",
+  "pdf",
+  "preview"
+]

AddedSep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only tell the agent this is not read-only and not destructive. The description adds the behavior that actually matters: the call is asynchronous, takes ~15-60 s, returns a jobId that must be polled via get_export, that 'preview' is returned inline (a non-obvious response shape), and that an API key with the export scope is required. No contradiction with the annotations.

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?

Front-loaded with the core action and async behavior, and every sentence carries information. It is dense and a couple of clauses run long ('render one after every save, check the layout, cover art, text sizes and colours...'), but nothing is 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, and the description compensates by explaining the return value (jobId plus inline preview image) and the polling follow-up. With a required designId sourced from save_design/list_designs and only two parameters, nothing an agent needs to call this correctly is missing.

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, but the description genuinely extends the enum semantics: 'preview' is a downscaled whole-sheet image returned inline, 'png' is 600 DPI full-resolution, 'pdf' is design-size, and both print outputs are members-only. That is real added meaning beyond the schema's one-line enum labels.

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?

States a specific verb and resource ('Render a saved design') and immediately clarifies it is asynchronous ('Queues a job ... returns a jobId'), which separates it cleanly from get_export. The sibling set contains both get_export and get_design, and this description makes clear which one is the trigger versus the poller.

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?

Gives an explicit workflow: render a 'preview' after every save, verify layout/cover art/text/colours, fix intent and save again, then export 'png' or 'pdf' once the preview looks right. It also states the gating conditions for the full-resolution outputs ('members only, and only once the preview looks right'). This is unusually complete when-to-use guidance.

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

All Tapercraft — VHS Label Maker tools Inspect

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

Need Help?