Tutorial AI

List assets

list_assets

Read-only

List the images and videos stored in one workspace. Either kind can be placed on a slide through update_slide elements.add or add_slide elements. Returns {assets, total, hasMore}. Each asset has a uid, display name, mimeType, upload status and pixel dimensions, plus durationMs (the usable video duration in milliseconds, or null). Use durationMs for video trim. After a local upload, poll at reasonable intervals for up to 2 minutes for status "uploaded". If it is still uploading, stop polling and report that background upload finalization is unavailable. assets is one page, capped at 100; answer "how many" from total, never by counting the returned assets.

Input Schema

Name	Required	Description
`type`	No	Restrict to images or to videos. Both are listed when omitted.
`limit`	No	Assets per page. Defaults to 25, silently capped at 100.
`query`	No	Case-insensitive filter on the asset name
`offset`	No	Assets to skip, for reading past the first page. Defaults to 0.
`workspaceUid`	Yes	From list_workspaces

Output Schema

Name	Required	Description	Default
`total`	Yes
`assets`	Yes
`hasMore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026
- removedOutput schema / properties / assets / items / properties / height / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / assets / items / properties / height / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / assets / items / properties / width / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / assets / items / properties / width / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the real behavioral load: page cap of 100, one-page-per-call pagination, a 2-minute polling ceiling for upload status, and the explicit fallback 'background upload finalization is unavailable' when polling fails. Those operational traits are exactly what an agent cannot infer from annotations alone.

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?

Purpose is front-loaded in the first sentence, and the remaining sentences each carry operational guidance. It is slightly dense and repeats the 100 cap already in the schema, but nothing is wasted filler.

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

Completeness5/5

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

For a filtered, paginated list tool with an output schema and read-only annotations, the description covers scope, polling lifecycle, pagination limits, and how to report counts correctly. An agent has everything needed to call it and interpret results without guessing.

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 coverage is 100%, so the schema already defines type, limit, offset and query semantics. The description echoes the 100-asset cap and workspace scoping but adds no new parameter syntax or format detail beyond what the schema states, so the baseline 3 applies.

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 with explicit scope: 'List the images and videos stored in one workspace.' No sibling tool performs listing of assets, so the agent can route here without comparing schemas, and the sentence also implies the workspace-scoped boundary.

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?

Gives concrete downstream usage (place assets on slides via update_slide/add_slide), tells the agent to poll after a local upload and for how long, and warns to answer 'how many' from total. It stops short of naming explicit alternatives or exclusions, so it is strong context rather than full when/when-not routing.

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

All Tutorial AI 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?