Skip to main content
Glama
Sign In

Kuro

by com.meetkuro.api
OverviewDiscussionsAdmin

List uploads

list_uploads
Read-onlyIdempotent

Page through the account's uploads alone, newest first — list_media mixes them with generations. archived: true lists the archived ones instead. Each row carries the reference the generate tools take.

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_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
kindNo
limitNo
cursorNo
archivedNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
app_urlYes
has_moreYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedOutput schema / properties / items / items / description
      Added value: +"A file you brought into Kuro."
    • changedOutput schema / properties / items / items / properties / bytes / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / items / items / properties / created_at
      Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
    • addedOutput schema / properties / items / items / properties / id
      Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
    • removedOutput schema / properties / items / items / properties / kind
      Removed value: -{
-  "enum": [
-    "image",
-    "audio",
-    "video"
-  ],
-  "type": "string"
-}
    • addedOutput schema / properties / items / items / properties / object
      Added value: +{
+  "const": "upload",
+  "type": "string"
+}
    • changedOutput schema / properties / items / items / properties / reference / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "upload",
-        "type": "string"
-      },
-      "upload_id": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "upload_id"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "generation_id": {
-        "format": "uuid",
-        "type": "string"
-      },
-      "type": {
-        "const": "generation",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "generation_id"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "upload",
+        "type": "string"
+      },
+      "upload_id": {
+        "$ref": "#/properties/items/items/properties/id"
+      }
+    },
+    "required": [
+      "type",
+      "upload_id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "generation_id": {
+        "$ref": "#/properties/items/items/properties/id"
+      },
+      "type": {
+        "const": "generation",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "generation_id"
+    ],
+    "type": "object"
+  }
+]
    • addedOutput schema / properties / items / items / properties / reference / description
      Added value: +"Pass this where a request takes media."
    • addedOutput schema / properties / items / items / properties / status / description
      Added value: +"Only a `verified` upload can be used in a generation."
    • addedOutput schema / properties / items / items / properties / status / enum
      Added value: +[
+  "pending",
+  "verified",
+  "rejected",
+  "expired"
+]
    • addedOutput schema / properties / items / items / properties / type
      Added value: +{
+  "enum": [
+    "image",
+    "video",
+    "audio"
+  ],
+  "type": "string"
+}
    • removedOutput schema / properties / items / items / properties / upload_id
      Removed value: -{
-  "format": "uuid",
-  "type": "string"
-}
    • addedOutput schema / properties / items / items / properties / url / description
      Added value: +"A signed link to the file, for about an hour."
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "upload_id",
-  "filename",
-  "kind",
-  "mime_type",
-  "bytes",
-  "status",
-  "url",
-  "thumbnail_url",
-  "reference"
-]New value: +[
+  "object",
+  "id",
+  "filename",
+  "type",
+  "mime_type",
+  "bytes",
+  "status",
+  "url",
+  "thumbnail_url",
+  "reference",
+  "created_at"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / thumbnail_url
      Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "upload_id",
-  "filename",
-  "kind",
-  "mime_type",
-  "bytes",
-  "status",
-  "url",
-  "reference"
-]New value: +[
+  "upload_id",
+  "filename",
+  "kind",
+  "mime_type",
+  "bytes",
+  "status",
+  "url",
+  "thumbnail_url",
+  "reference"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: newest-first ordering, pagination semantics, the archived toggle, and the fact that each row exposes the `reference` consumed by the generate tools.

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

Conciseness5/5

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

Three short clauses, front-loaded with purpose and differentiation, then the archived variant, then the downstream-use detail. No filler, and every sentence carries information the schema does not.

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?

An output schema exists, so return shape needn't be spelled out, and the description usefully notes the `reference` field. But for a five-parameter list tool with zero schema documentation, leaving search/filter/limit behavior unaddressed is a visible gap.

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 description coverage is 0% for five parameters, so the description carries the full explanatory burden, yet it only clarifies `archived` (and implies `cursor` via "page through"). `q`, `kind` and `limit` are never mentioned, so an agent gets no meaning for three of the five inputs beyond their bare names.

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

Purpose5/5

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

States a specific verb and resource ("page through the account's uploads") plus scope ("alone", "newest first") and immediately distinguishes it from the sibling list_media, which "mixes them with generations." An agent can pick this tool over list_media without opening either schema.

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?

Explicitly names the alternative (list_media) and the condition that selects it, and gives the archived-vs-active switch via `archived: true`. It stops short of covering the remaining selection cases — e.g. when to filter with `q`/`kind` versus calling get_upload for a single item.

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

All Kuro toolsInspect
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