Tools
You never name these. You ask for an outcome and the assistant picks. They are listed so you know what is possible, and what is not.
Account
| Tool | |
|---|---|
whoami | Which team this connection acts on, who approved it, the plan, and credits left |
Templates
| Tool | |
|---|---|
list_templates | Your templates |
get_template | One template, including its document |
get_template_fields | What data this template accepts |
browse_library | Ready-made templates to start from. Search by what you need it for, not just its name |
create_template | A new one, from scratch, copied from the library, or an empty Word template |
update_template | Change the design or the settings |
validate_template | Check for problems before publishing |
preview_template | Render a preview as an image, of your template or of a library one you have not copied. Every engine, Word included. Free — no credit, no history entry |
Files
| Tool | |
|---|---|
upload_template_asset | Add an image the template can use. Inline, so only for small files |
list_template_assets | What a template can already refer to. An assistant checks this before naming a file, because naming one that was never uploaded is the most common way a first render fails |
create_upload_url | A link to send a file to. This is how files get in — an assistant cannot type out a real image or Word file as text. Takes a template's image or Word body, or a logo or font for the team's Brand Kit |
commit_upload | Store what was uploaded. The file is checked here before it goes live, and a Brand Kit upload adds rather than replaces — a name already in the kit is refused, because replacing it would change every template pointing at that key |
upload_template_docx | Replace a Word template's body. Inline, so only for small files |
download_template_docx | Get the Word file back, to edit it and put it back |
Versions
| Tool | |
|---|---|
list_template_versions | Every saved state of a template, newest first |
restore_template_version | Put it back to an earlier one. Adds a version rather than erasing any |
Rendering
| Tool | |
|---|---|
render_document | Produce a document. Costs a credit |
get_render | Fetch one, including a link you can share |
Dynamic URLs
| Tool | |
|---|---|
create_dynamic_url | One permanent address that renders on request |
list_dynamic_urls | All of them, with usage |
update_dynamic_url | Expiry, render limit, cache lifetime, formats, disable — and pin it to one template version so editing the template cannot change what it serves |
add_dynamic_url_secret | A new signing secret. The old ones keep working |
revoke_dynamic_url_secret | Immediate, and it breaks anything still using it |
Forms
| Tool | |
|---|---|
list_forms | Your forms |
get_form | One form, with its questions |
create_form | Build one |
update_form | Change one |
connect_form_template | Generate a document from each submission |
publish_form | Make it live |
list_form_submissions | What people have sent |
Webhooks
| Tool | |
|---|---|
list_webhooks | Your endpoints |
create_webhook | Add one |
test_webhook | Send a test delivery |
delete_webhook | Remove one |
Brand
| Tool | |
|---|---|
get_brand_kit | Your colours, logos and fonts, so generated designs match |
Reference
| Tool | |
|---|---|
read_skill | Our own documentation, handed over on request: how each template format works, the component and property tables, the font catalogue with its known gaps, and worked examples. An assistant is told to read this before writing anything |
Preview is free, rendering is not. Authoring is iterative, so an assistant
can look at its work as often as it needs. Only render_document costs a
credit and appears in History.
This includes library designs: preview_template with from_library fills a
library template with your words and shows it to you without copying it, so
choosing between two certificates does not cost a template slot.
Getting files in and out
An assistant cannot type out a real file. A tool call is text it writes one
character at a time, so a 36KB Word template is fifty thousand characters that
have to be perfect — which is why create_upload_url exists: it hands back a
link, the file goes straight to storage, and only a reference passes through the
conversation.
The inline tools remain for small things an assistant genuinely produced, such as an SVG it drew.
Every save is kept
Changing a template does not overwrite it. Each save is stored, so an assistant can show you what changed and put it back if an edit went wrong, and a Dynamic URL can be frozen to one version when a link is already embedded somewhere you cannot edit.
What is deliberately absent
No bulk render. An assistant loops render_document instead. A bulk tool
would let one confused request spend a thousand credits.
No template deletion. Destructive and irreversible; it stays in the dashboard where there is a confirmation and a trash.
No writing a Word file from scratch. An assistant can upload one, fetch it, edit it and put it back, and it can tell you exactly which placeholders to add — but a .docx is a real file, not something that can be written as text.
Nothing that calls our own AI. Every tool is a direct operation. The intelligence is the assistant you connected.
Last updated on