Skip to main content
Glama

List a site's photos

list_photos
Read-only

Lists the photos uploaded for a site with their asset ids, sizes, descriptions (alt text) and the storage used. Use the asset ids in gallery sections and as the theme logo.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description goes beyond them by disclosing the actual returned fields (asset ids, sizes, alt text, storage used) — valuable because there is no output schema. It stops short of describing ordering, pagination, or behavior on an empty or invalid site.

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?

Two sentences, zero filler, with the core behavior front-loaded before the downstream usage hint. Each sentence carries distinct information — one describes the return payload, the other tells the agent how to consume the ids.

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 one-parameter read-only list tool with annotations and no output schema, the definition covers purpose, return contents, and downstream use adequately. Remaining gaps — result ordering, pagination or size limits on a potentially large photo collection, and empty-state behavior — are minor but real for a listing endpoint.

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?

There is a single parameter with 100% schema description coverage; the schema already says site_id comes from list_sites or create_site. The description only implies site scoping ("for a site") without adding format, sourcing, or constraint detail beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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?

"Lists the photos uploaded for a site" gives a specific verb and resource, and the description immediately enumerates what comes back (asset ids, sizes, alt text descriptions, storage used). That return inventory separates it cleanly from sibling mutations like delete_photo and update_photo, which operate on a single photo rather than enumerating a site's collection.

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?

"Use the asset ids in gallery sections and as the theme logo" explains what to do with the output, which implies when to reach for this tool. It never states when not to use it, gives no prerequisites (e.g. site must exist, auth scope), and does not name a sibling alternative such as get_site for broader site data. Usage is inferable but not spelled out.

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