Skip to main content
Glama
Sign In

CueFrame

by ai.cueframe
OverviewDiscussionsAdmin

List Media

list_media
Read-onlyIdempotent

List the media in your CueFrame library. Filter a real library with kind (video|audio|image|gif|asset|source|stock), source (upload|generated|import-url|stock), or tag — so you find YOUR footage, not e2e debris. Returns media item IDs and metadata; use an ID with get_media_context, suggest_briefs, or as a composition source.

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

Input Schema

NameRequiredDescriptionDefault
tagNoFilter to items carrying this EXACT tag (not a prefix or substring match).
kindNoFilter to one media kind.
afterNoOpaque cursor from the previous page's `pagination.nextCursor`. Forward-only.
limitNoPage size (1..100), default 20. Out-of-range or unparseable clamps into the range.
sourceNoFilter by how the item entered the library.
projectIdNo

Output Schema

NameRequiredDescriptionDefault
dataNo
paginationNoCursor pagination metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / projectId
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and an output schema covers the return shape, so the description only needs to add context — which it does by stating that IDs feed get_media_context/suggest_briefs and that results are the real library rather than e2e fixtures. It does not mention pagination behavior, though the `after`/`limit` schema fields carry that.

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 sentences, front-loaded with the core action, then filters, then return/next-step guidance. The inline enum enumeration duplicates the schema slightly, but it lets an agent choose filters without opening the schema.

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?

With an output schema present the description needn't explain return values, and the annotations handle safety, so what remains — filters, real-vs-test scope, and the ID-chaining workflow — is covered. The only gap is projectId, which is undocumented in both schema and description, leaving the agent to guess that ambiguity.

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 83%, so the schema already documents tag (exact match), kind, source, after, and limit. The description echoes the filter names and enumerates most kind/source values but adds no semantics beyond the schema, and it never mentions projectId, which has no schema description at all. 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 ("List the media in your CueFrame library") plus the available filter dimensions, which separates it cleanly from list_projects, list_compositions, and list_catalog. It also names the downstream consumers of the returned IDs, so the agent knows exactly what this tool produces.

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?

Clear about when this is the right call (browsing real library assets rather than test debris) and explicitly routes to get_media_context, suggest_briefs, or composition sourcing once an ID is in hand. It does not name an alternative listing tool to use instead when, e.g., the agent wants catalog/stock browsing, so it stops short of full when-not coverage.

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

All CueFrame 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