Skip to main content
Glama

list_media

Browse Strapi Media Library files to find existing images or documents, verify uploads, and retrieve file names, IDs, dimensions, MIME types, and alt text.

Instructions

Browse files in the Strapi Media Library (images, documents, etc.). Returns file names, IDs, dimensions, MIME types, and alt text. Use this to find existing media files or verify uploads.

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
pageNoPage number (default 1)
page_sizeNoItems per page (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden; it does describe the returned fields, which is valuable given there is no output schema. However, it never states that the operation is read-only/non-mutating, nor anything about permissions, page limits, or total-count behavior, leaving meaningful behavioral gaps for an unannotated tool.

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 tight sentences: what it browses, what it returns, and when to use it. Front-loaded and free of filler.

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, two-parameter paginated listing with no output schema, the description covers purpose, return contents, and usage context adequately. The main remaining gap is that it does not explicitly confirm the read-only nature or note pagination limits given the absence of annotations.

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%, with page and page_size already documented including their defaults. The description adds no additional meaning about pagination semantics (e.g., max page_size, how to walk pages), so the schema does all the work and the baseline of 3 applies.

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?

States a specific verb and resource ("Browse files in the Strapi Media Library") and enumerates the returned fields (names, IDs, dimensions, MIME types, alt text). This clearly separates it from the write-side siblings upload_media and update_media, though it never names them explicitly.

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?

"Use this to find existing media files or verify uploads" gives a concrete when-to-use context that an agent can act on. There are no explicit exclusions or named alternatives (e.g., upload_media for adding files), so it stops short of the top band.

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