Skip to main content
Glama

List a site's uploaded images

list_images
Read-only

The images uploaded to a site, newest first: URL, upload time and whether the draft already uses it. Call it when the owner says they uploaded images and you do not have the URLs, and before asking for photos again. Place a URL with update_site. Original file names are not kept.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses newest-first ordering, the returned fields, and the important caveat that original file names are not kept. That is substantial behavioral and output context for a read-only listing 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?

The description is compact and front-loaded with the main resource and return shape. Each sentence adds practical value: usage trigger, follow-up action, and the filename caveat.

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 read-only tool with one parameter and no output schema, it covers usage, ordering, returned fields, and a key data caveat. The one notable omission is siteId semantics, though the parameter is otherwise self-evident.

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

Parameters2/5

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

The only parameter is siteId, and schema description coverage is 0%. The description only implies that it is the site whose uploaded images are listed; it does not explain the UUID format, how to obtain the siteId, or any other parameter-level detail.

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 clearly states the resource ('images uploaded to a site'), the ordering ('newest first'), and the returned fields (URL, upload time, draft usage). It is distinguishable from update_site and from asking the owner for photos again.

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 a specific trigger: when the owner says they uploaded images and you do not have the URLs, and before asking for photos again. It also says to place a URL with update_site. It does not explicitly state when not to use this tool or name a direct alternative list tool.

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