post_v1_o11y_reviews_id_items

AddAnnotationQueueItems enqueues traces, observations or sessions on a review queue.

AddAnnotationQueueItems enqueues traces, observations or sessions on a review queue. Each item names exactly one object, either by traceId / observationId / sessionId or by objectType plus objectId; every item enters PENDING. A queue id belonging to another org is a 404.


Tool	`post_v1_o11y_reviews_id_items`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2
Operation	`POST /v1/o11y/reviews/{id}/items`
Product	o11y

Arguments

Field	Type	Required	Default	Values	Description
`id`	`string`	—	—	—	ID is the annotation queue to add to, from the path.
`items`	`itemInput[]`	—	—	—	Items are the objects to enqueue for review, 1–200 per request. Each names exactly one object.

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.

Object types

itemInput is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

itemInput

Field	Type	Required	Default	Values	Description
`assignee`	`string`	—	—	—	Assignee is the reviewer this item is for, up to 512 characters.
`objectId`	`string`	—	—	—	ObjectID is the referenced object's id, paired with objectType.
`objectType`	`string`	—	—	—	ObjectType is TRACE, OBSERVATION or SESSION — the generic form, paired with objectId.
`observationId`	`string`	—	—	—	ObservationID references an observation — the console-friendly form of objectType=OBSERVATION.
`sessionId`	`string`	—	—	—	SessionID references a session — the console-friendly form of objectType=SESSION.
`traceId`	`string`	—	—	—	TraceID references a trace — the console-friendly form of objectType=TRACE.

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_o11y_reviews_id_items",
         "arguments": {
           "id": "<id>",
           "items": [
             {
               "assignee": "<assignee>",
               "objectId": "<objectId>",
               "objectType": "<objectType>",
               "observationId": "<observationId>",
               "sessionId": "<sessionId>",
               "traceId": "<traceId>"
             }
           ]
         }
       }
     }'

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_o11y_reviews_id_items`	`POST /v1/o11y/reviews/{id}/items`	o11y	Enqueues traces, observations or sessions on a review queue.

The same capability over plain HTTP is in the o11y 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).