Skip to main content
Glama

List photo sets and download links

list_photo_sets
Read-only

Recent AI photo sets of the account's catalog, newest first, with render status and, when done, a zip download link and each image's view/download links (square 2000x2000 and portrait 1080x1350).

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_photo_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: results are ordered newest first, render status is included, and download links only appear once a set is 'done' — this state-dependency is the key behavioral fact an agent needs. It stops short of explaining pagination or what an incomplete render returns.

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?

A single front-loaded sentence that leads with the resource and then layers on payload detail with no filler. The trailing parenthetical with both resolutions is dense but carries real information an agent would otherwise lack.

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?

With no output schema, the description carries the full burden of describing returns and does so well — ordering, status field, and both link types. Since there are no required parameters the tool is callable as-is, but the omission of limit/pagination behavior leaves a real gap for an agent trying to enumerate the full catalog.

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?

Schema description coverage is 0% for the single 'limit' parameter (integer, default 12, max 50), so the schema supplies no meaning and the description must compensate. It never mentions the limit, the default of 12, the 50 cap, or whether the tool paginates; the word 'Recent' is the only weak hint that the result set is bounded.

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 names a specific verb and resource (list recent AI photo sets of the account's catalog) and specifies the returned payload in detail: render status, zip link, per-image view/download links with both resolutions. It does not explicitly distinguish itself from the many sibling list_* tools (list_creations, list_static_ads, list_carousels), so an agent must infer the boundary from the resource noun, but the resource itself is unambiguous.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only guidance is implicit — the mention of 'render status and, when done, ... download links' hints at a poll-then-fetch workflow, but nothing states whether this should be called instead of list_creations or after generate_photos.

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.