Skip to main content
Glama

PhotoShelter MCP Server and API by Cotlet

Search images in PhotoShelter

photoshelter_search_images
Read-onlyIdempotent

Search images in the user's own PhotoShelter account from ChatGPT, Claude or any AI agent. Returns how to do it in PhotoShelter step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's PhotoShelter Cloud Browser. PhotoShelter's official API: PhotoShelter publishes API documentation, but customers contact support to get an API key instead of generating one (checked 8 Nov 2026).

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": "photoshelter_search_images"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description reinforces this usefully with "opens nothing by itself" and discloses the API-key procurement constraint, which is genuine extra context. It does not describe the shape or size of the returned instructions (e.g., length, whether it includes verification steps).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core facts (returns instructions, opens nothing, then use browser tools) are present but arrive after marketing filler like "from ChatGPT, Claude or any AI agent." The API-key sentence is relevant yet awkwardly phrased, repeating "PhotoShelter" and burying the actionable point (no self-serve key) behind preamble.

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 zero-parameter, no-output-schema guide tool, the description covers what comes back (screens, buttons, fields) and what does not happen (no action taken), which is what an agent needs before calling. The one remaining gap is what the agent should do if the returned instructions do not match the live UI.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. It correctly avoids inventing parameter-like concepts such as a search query field, which prevents the agent from trying to pass arguments the schema rejects.

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 ("Search images in the user's own PhotoShelter account") and immediately clarifies the real deliverable: step-by-step instructions rather than search results. It does not explicitly contrast itself with the gallery/caption siblings, and the opening sentence's "Search images" framing briefly implies direct execution before being corrected.

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 clear workflow split: this tool returns the procedure, then "do it with the cotlet_browser_* tools in the user's PhotoShelter Cloud Browser," which routes the agent to the right alternatives. It stops short of stating when this tool is unnecessary (e.g., if the agent already knows the flow) or how it relates to cotlet_app_guide.

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.