post_v1_prompts
Create records a prompt for the caller's org and answers 201 with it.
Create records a prompt for the caller's org and answers 201 with it. A name the org already uses is NOT an error and NOT an overwrite: it appends a new version, so the library keeps real, inspectable history and the response carries the whole version list. The name is also the URL segment the prompt is fetched by, which is why its shape is constrained and a handful of names are reserved.
| Tool | post_v1_prompts |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | POST /v1/prompts |
| Product | prompts |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
labels | string[] | — | — | — | Labels is free-form taxonomy, each up to 64 characters, capped at 32 entries. |
name | string | — | — | — | Name is the org-unique handle AND the URL segment the prompt is addressed by: 1-64 characters matching ^[A-Za-z0-9][A-Za-z0-9._-]*$. "metrics", "new" and "catalog" are reserved. A name that already exists appends a new version. |
prompt | string | — | — | — | Prompt is the template body, capped at 64 KiB. It holds template text only — never a secret. |
tags | string[] | — | — | — | Tags is free-form taxonomy under the same bounds as Labels. |
type | string | — | — | — | Type labels the template's kind; defaults to "text". |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_prompts",
"arguments": {
"labels": [
"<labels>"
],
"name": "<name>",
"prompt": "<prompt>",
"tags": [
"<tags>"
],
"type": "<type>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_prompts | POST /v1/prompts | prompts | Create records a prompt for the caller's org and answers 201 with it. |
The same capability over plain HTTP is in the prompts API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?