Kuro

List reusable media

list_media

Read-onlyIdempotent

List ready generations and verified uploads already in the user's account, newest first. Each item carries a reference the generate tools accept as-is — for guided recipe slots, first/last frames, or reference images. Pass favorite:true for the starred ones, or tags for the items carrying every tag named — tags are how work is grouped (a client, a campaign). The first 10 items that have one come back as pictures you can look at, in list order; narrow with q/kind or lower the limit to see the ones you care about rather than paging for them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No
`kind`	No
`tags`	No
`limit`	No
`cursor`	No
`favorite`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`app_url`	Yes
`has_more`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / tags

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

addedOutput schema / properties / items / items / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / items / items / properties / user_tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "source",
-  "id",
-  "kind",
-  "title",
-  "status",
-  "preview_url",
-  "favorite",
-  "reference"
-]New value: +[
+  "source",
+  "id",
+  "kind",
+  "title",
+  "status",
+  "preview_url",
+  "favorite",
+  "tags",
+  "user_tags",
+  "reference"
+]

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, so the safety burden is removed. The description adds genuinely new behavioral context beyond the annotations: newest-first ordering, that each item exposes a `reference` consumable by the generate tools, and that only the first 10 items with a thumbnail return as viewable pictures in list order.

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?

Front-loads the core purpose, then layers filtering and return behavior. It is a single dense block and slightly meandering in the tags clause, but each sentence carries operational information and nothing is pure filler.

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

Completeness4/5

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

An output schema exists so return shape needn't be spelled out, and annotations cover safety. The description fills in ordering, filter semantics, and the 10-image multimodal cap, leaving only cursor-based paging under-explained for a six-parameter list tool.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does cover most: favorite=starred, tags=AND semantics over named tags (with grouping rationale), plus hints for q, kind, and limit. Cursor is never mentioned and q's nature (text search) is only implied, leaving real gaps given the zero schema documentation.

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?

States a specific verb (list) and resource, and scopes it precisely as 'ready generations and verified uploads already in the user's account', which implicitly separates it from the broader list_generations/list_uploads siblings. It does not name those siblings explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Gives concrete guidance on filtering ('Pass favorite:true', 'narrow with q/kind or lower the limit') and on avoiding paging, which is useful. However it never states when to reach for this tool versus list_generations or list_uploads, so the alternative-selection question is left to inference.

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?