Skip to main content
Glama

List media library

list_media

List the media library of the API key's workspace, newest first (id, url, mediaType).

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
sortNoOrdering; "newest" (default, newest first) is the only supported value.
limitNoPage size, 1-100 (default 20).
offsetNoItems to skip (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: results are scoped to the API key's workspace and ordered newest first, and the returned fields are named. It stops short of stating that the operation is read-only-in-effect or describing what happens at the end of the result set, but the core behavioral profile is clear.

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?

A single compact sentence with the scope and ordering information front-loaded and no redundant phrasing. Every clause (workspace scope, ordering, returned fields) carries information.

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?

For a simple paginated read with fully described parameters and no output schema, the description supplies the ordering and the shape of returned items, which is the important missing piece. It could note pagination behavior (whether offset/limit page through a larger set) but nothing essential to correct invocation is absent.

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 100%, so sort, limit, and offset are already fully documented, and the description's "newest first" merely restates the default sort value. It adds no syntax, bounds, or interaction detail beyond the schema, which is the expected baseline here.

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?

The description gives a specific verb and resource, "List the media library," and adds a scope qualifier, "of the API key's workspace," plus the returned fields (id, url, mediaType). That is enough to separate it from the only closely related sibling, upload_media, though the distinction is implied by the verb rather than stated outright.

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?

Usage is only implied: an agent can infer this is the way to enumerate existing media items, but the description never says when to call it instead of alternatives (for example, before upload to check for duplicates) or what the pagination workflow looks like. No exclusions or prerequisites are stated.

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