Skip to main content
Glama

List images

list_media
Read-onlyIdempotent

List the images the user uploaded to their media library on the web: id, name, width, height, aspect_ratio (width/height), bytes, mime and created_at, newest first, plus used_bytes. Pass an id to add_objects to place the picture on a slide. You cannot upload an image or fetch one from a web address; if the picture you need is missing, ask the user to upload it to their media library on the web. Pass scope "team" to list the team library instead (images every team member can use in team templates). Needs an API key; works on any plan.

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
scopeNo"personal" (default) lists the user's own images; "team" lists the team library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scope / description
      Added value: +"\"personal\" (default) lists the user's own images; \"team\" lists the team library."
  2. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
      +  "enum": [
      +    "personal",
      +    "team"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-derivable context: results are newest first, a used_bytes total is included, an API key is required, and the tool works on any plan. It stops short of disclosing pagination or result-count limits, which matters for a list operation on a potentially large library.

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?

The first sentence front-loads purpose plus return fields, and each subsequent sentence carries a distinct fact (placement path, upload limitation, scope switch, auth). It is dense but not padded; the field enumeration is long, though it substitutes for a missing output schema.

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?

With no output schema, the description compensates by listing exactly what each record contains and adding the aggregate used_bytes. Combined with the upload limitation, scope semantics, and auth note, an agent has everything needed to call this correctly and interpret the result.

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?

Schema coverage is 100% and the single enum parameter is already documented, so the baseline would be 3. The description adds meaning beyond the schema by explaining that "team" yields images every team member can use in team templates, which clarifies the practical consequence of the enum value rather than just restating it.

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 names a specific verb and resource ("List the images the user uploaded to their media library") and enumerates the returned fields (id, name, width, height, aspect_ratio, bytes, mime, created_at, used_bytes). It also distinguishes itself from the write-side sibling by pointing at add_objects for placement, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use context (listing media before placing an image), a concrete alternative for a related task ("Pass an id to add_objects to place the picture on a slide"), and a clear when-not/capability boundary: you cannot upload or fetch from a URL, so ask the user to upload instead. It also tells the agent how to reach the team variant via scope "team".

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