Kuro

List subjects

list_subjects

Read-onlyIdempotent

The named identities this account reuses — a character, a location, a product, a prop, a wardrobe. Each item carries a subject handle the generate tools take as-is: passing it supplies that identity's face and its description together, so you do not have to find a reference file or re-describe it. Check this before list_media. tags narrows to the subjects carrying every tag named.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_subjects"
  }
}

Input Schema

Name	Required	Description
`q`	No
`kind`	No
`tags`	No
`limit`	No
`order`	No
`cursor`	No	The `next_cursor` of the page before this one.
`favorite`	No

Output Schema

Name	Required	Description	Default
`app_url`	Yes
`message`	Yes
`subjects`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedNov 4, 2026

addedOutput schema / properties / subjects / items / description

Added value: +"Someone or something you make again and again. Name it in `subjects` and Kuro brings its face and description."

addedOutput schema / properties / subjects / items / properties / app_url / $ref
```
Added value: +"#/properties/subjects/items/properties/preview_url/anyOf/0"
```
removedOutput schema / properties / subjects / items / properties / app_url / format
```
Removed value: -"uri"
```
removedOutput schema / properties / subjects / items / properties / app_url / type
```
Removed value: -"string"
```
addedOutput schema / properties / subjects / items / properties / created_at
```
Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
```

addedOutput schema / properties / subjects / items / properties / has_voice

Added value: +{
+  "description": "Whether a voice is bound to it, for voice-overs.",
+  "type": "boolean"
+}

addedOutput schema / properties / subjects / items / properties / id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```

addedOutput schema / properties / subjects / items / properties / identity_images / description

Added value: +"How many reference pictures travel with it. Zero: it travels as words alone."

changedOutput schema / properties / subjects / items / properties / identity_images / type
```
Previous value: -"number"New value: +"integer"
```

addedOutput schema / properties / subjects / items / properties / kind / description

Added value: +"\"character\", \"location\", \"product\", \"prop\" or \"wardrobe\". New values may be added."

removedOutput schema / properties / subjects / items / properties / kind / enum

Removed value: -[
-  "character",
-  "location",
-  "product",
-  "prop",
-  "wardrobe"
-]

addedOutput schema / properties / subjects / items / properties / object
```
Added value: +{
+  "const": "subject",
+  "type": "string"
+}
```
removedOutput schema / properties / subjects / items / properties / subject_id
```
Removed value: -{
-  "format": "uuid",
-  "type": "string"
-}
```

changedOutput schema / properties / subjects / items / required

Previous value: -[
-  "subject_id",
-  "name",
-  "kind",
-  "description",
-  "prompt_fragment",
-  "identity_images",
-  "identity_object_ids",
-  "voice",
-  "tags",
-  "favorite",
-  "preview_url",
-  "appearance_count",
-  "subject",
-  "app_url"
-]New value: +[
+  "object",
+  "id",
+  "name",
+  "kind",
+  "description",
+  "identity_images",
+  "has_voice",
+  "tags",
+  "preview_url",
+  "created_at",
+  "app_url",
+  "prompt_fragment",
+  "identity_object_ids",
+  "voice",
+  "favorite",
+  "appearance_count",
+  "subject"
+]

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / tags

Added value: +{
+  "items": {
+    "maxLength": 40,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 8,
+  "minItems": 1,
+  "type": "array"
+}

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds meaningful payload context beyond that: each result carries a `subject` handle consumed as-is by the generate tools, bundling face plus description. It omits pagination behavior entirely despite a `cursor`/`limit` pair, which is the main behavioral gap for a filtered list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with no filler: identity definition, why the handle matters, routing to list_media. The ordering is slightly off — the sibling comparison sits last where it would help more up front — but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter filtered list with an output schema, the description covers the what and the why well but leaves most filter parameters and all paging behavior unstated. An agent can find subjects, but cannot confidently predict what `q`, `order`, `favorite`, or `limit` will do from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 14% — just `cursor` is documented in the schema — so the description carries the burden and largely doesn't. It does add genuinely useful meaning for `tags` (narrows to subjects carrying every named tag, i.e. AND semantics), but `q`, `kind`, `limit`, `order`, and `favorite` go entirely unexplained in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource concretely — 'the named identities this account reuses' with the exact `kind` values (character, location, product, prop, wardrobe) — and implicitly conveys enumeration by describing what each item carries. It distinguishes the tool from list_media by name, but never states a plain listing verb, so the read operation is inferred rather than declared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing guidance: 'Check this before list_media' and explains the payoff — passing the `subject` handle supplies that identity's face and description without hunting for a reference file. What's missing is any when-not guidance (e.g., use get_subject_performances instead if you need usage stats) and any note on paging through many results, but the core use case is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kuro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?