Skip to main content
Glama

List Site Photos

list_site_photos
Read-onlyIdempotent

List images the user has previously uploaded to their photo library for this site (the 'My Photos' library at /photos in Zarla — real photos of their work, NOT stock images). ALWAYS check here first when the user asks you to use 'their photos', 'photos of my work', 'pictures from my last job', or similar. Returns the newest 100 image URLs, which you can pass directly to update_block (image / images), update_business_info, or update_seo. If this returns 0 photos, the user hasn't uploaded any yet — at that point, ask if they'd like to upload some via request_image_upload, or fall through to stock imagery.

Annotations: read-only=true, destructive=false, idempotent=true, open-world=false. Why: Reads data only and changes nothing (read-only, so trivially idempotent). Closed-world: it touches only Zarla's own database.

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

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status. Default "all". The photo library has no drafts — "draft" always returns 0 photos; use "all" (or omit).
site_idYesThe site this photo library belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, so the safety profile is covered. The description adds genuinely new behavior: the result set is capped at the newest 100 URLs, the library has no draft photos, and an empty result means the user has never uploaded. It does not describe URL format or expiry, which would be the remaining useful detail.

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?

Front-loaded with the purpose and the 'NOT stock images' warning, then triggers, then return shape, then the zero-result escape hatch. Dense and mostly waste-free, though the em-dash aside about the /photos path and the mild restatement of 'real photos of their work' could be trimmed slightly.

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 carries the return contract (newest 100 image URLs, directly consumable by named tools) and the empty-case behavior, which is exactly what an agent needs to act on the result. Parameter quirks are handled by the schema, so nothing material is missing.

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% and the status enum already explains that 'draft' always returns 0 and 'all' is the default. The description says nothing about site_id or status, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource (list images the user uploaded to their photo library for this site) and disambiguates the resource from stock imagery with a concrete path reference (/photos). An agent can tell immediately this is the user's own work photos, not a generic asset search.

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?

Gives an explicit trigger ('ALWAYS check here first') with sample user phrasings, names the downstream tools the output feeds (update_block, update_business_info, update_seo), and handles the zero-result branch by routing to request_image_upload or stock imagery. When/when-not and the empty-result fallback are both 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.