Appearance
Templates
Branded documents generated from your data.
7 tools — 4 read, 3 write.
| Tool | What it does | |
|---|---|---|
delete_template | write | Permanently delete a template. |
get_template | read | Fetch a template's full definition — chrome (page geometry, header/footer, css), ordered blocks, inputs JSON Schema, formats, and audit fields. |
get_template_schema | read | Fetch a template's metadata + inputs JSON Schema. |
list_templates | read | List all HTML templates registered in the active org, ordered most-recent-first. |
register_template | write | Register a deterministic, block-based template that renders to a PDF (server-side via WeasyPrint). |
render_template | read | Render a registered template with the given inputs. |
update_template | write | Partially update an existing template (id or slug). |
Calling these
Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.
See How the API works for auth, errors and the shared envelope.