Skip to main content
Glama

PhotoShelter MCP Server and API by Cotlet

Update captions and keywords in PhotoShelter

photoshelter_update_captions_and_keywords
Read-onlyIdempotent

Update captions and keywords 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_update_captions_and_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotent), and the description adds genuinely new behavior: nothing is opened or changed by the call itself, the return value is step-by-step UI guidance, and the official API key cannot be self-generated. That last note usefully explains why browser automation is the path; rate limits and per-image constraints are not mentioned.

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?

Three sentences, each carrying information, with the no-side-effects clause and the browser-tool handoff stated plainly. Minor waste in the marketing phrase 'from ChatGPT, Claude or any AI agent' and the somewhat tangential API-key aside, but no sentence is redundant overall.

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 parameterless guide tool with no output schema, the description explains what comes back (screens, buttons, fields), that nothing executes, and what to do next. Missing only edge-case context such as login prerequisites or whether the Cloud Browser must already be open.

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. The description adds nothing about inputs because there are none, and correctly introduces no ambiguity about hidden arguments.

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+resource and then clarifies the real function: it returns step-by-step instructions (screens, buttons, fields) rather than performing the edit, and points at the cotlet_browser_* tools for execution. The first sentence mostly restates the tool name and 'from ChatGPT, Claude or any AI agent' is filler, so the operationally important distinction arrives second rather than up front, but an agent can still identify the tool against its siblings.

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 context: call this to obtain the PhotoShelter steps, then execute with cotlet_browser_* in the user's Cloud Browser. It does not say when not to use it or contrast it with cotlet_app_guide / photoshelter_search_images, so the routing guidance is clear but incomplete.

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.