Skip to main content
Glama

Your images and videos

list_media
Read-onlyIdempotent

Images and videos you made, newest first, optionally for one character, of one type or for one brand, with links that expire in an hour. Each says the brand it was made for (workspaceBrandId, with its name, kept after that brand is deleted) and where it lists (workspaceKey: a brand id or "_unassigned"; null for media made before brands were recorded, which list only without a brand filter). Use an id as startImageMediaId or referenceMediaIds when generating, or as mediaIds when scheduling. Page with nextCursor.

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
typeNo
limitNo
cursorNoThe nextCursor from the previous page
brandIdNoOnly media made for this brand (an id from list_brands), or "unassigned" for media made for no brand or for a deleted one
characterIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive behavior, and the description layers on substantial extra context: newest-first ordering, links that expire in an hour, brand attribution retained after a brand is deleted, and the null workspaceKey semantics for pre-brand media. These are non-obvious behavioral traits an agent could not infer from the annotations or schema.

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 and ordering are front-loaded in the first clause, and every sentence carries real information about filters, returned fields, or id reuse. The middle sentence is dense with nested parentheticals, which slightly slows parsing but does not waste words.

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?

There is no output schema, and the description compensates by naming key returned fields (workspaceBrandId with name, workspaceKey, expiring links, nextCursor), so an agent knows what comes back. What remains unstated is the page-size default and the full shape of each media item, which is a modest gap for a read-only list tool.

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

Parameters4/5

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

With only 40% schema description coverage across five parameters, the description does real work: it maps the character, type, and brand filters to behavior, clarifies the brand/"unassigned" filtering effect, and explains that nextCursor drives paging. The limit parameter is never mentioned, leaving one gap.

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?

The description opens with a concrete verb-and-resource statement ("Images and videos you made, newest first") plus the filterable dimensions (character, type, brand). An agent can immediately tell this is the media-listing tool rather than the brand, character, or job listers among the siblings.

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 clear usage context for the filters and explicitly tells the agent how to reuse a returned id downstream (startImageMediaId/referenceMediaIds for generation, mediaIds for scheduling), which is valuable routing guidance. It stops short of stating when-not to use it or naming an alternative listing tool, so it is not a full when/when-not specification.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources