Hanzo
Cloud MCPhelp

post_v1_help_tickets

Files a customer support ticket into the public help center.

Files a customer support ticket into the public help center. It creates the ticket (status Open, source portal) with the customer's message on the description, then records that same message as the opening entry of the ticket's conversation thread; the description carries it regardless, so failing to write that entry loses nothing. Answers 201 with an opaque reference.

A deployment with no help center answers 404, one whose center has not installed the Help model answers 503, and a body over 64 KiB answers 413 — in that order, which is the order the route has always decided them in.

Toolpost_v1_help_tickets
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments4
OperationPOST /v1/help/tickets
Producthelp

Arguments

FieldTypeRequiredDefaultDescription
descriptionstringDescription is the customer's message. Optional; it becomes the ticket's description AND the opening entry of its conversation thread. Clipped at 16 KiB.
emailstringEmail is how the support team replies. Required; clipped at 320 characters (the RFC 5321 maximum). It is recorded as the ticket's customer, and it is not verified.
prioritystringPriority is Low, Medium, High or Urgent, case-insensitively. Anything else — including omitting it — is recorded as Medium rather than refused.
subjectstringSubject is the one-line summary of the problem. Required; longer than 300 characters is clipped rather than refused.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

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_help_tickets",
         "arguments": {
           "description": "<description>",
           "email": "<email>",
           "priority": "<priority>",
           "subject": "<subject>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. 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

OperationRouteProductSummary
cloud_post_v1_help_ticketsPOST /v1/help/ticketshelpFiles a customer support ticket into the public help center.

The same capability over plain HTTP is in the help API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page