Skip to main content
Glama

PhotoShelter MCP Server and API by Cotlet

Share gallery in PhotoShelter

photoshelter_share_gallery
Read-onlyIdempotent

Share gallery 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_share_gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the tool returns a procedural guide with screens, buttons, and fields, and performs no side effects. The note about API keys requiring support contact explains why browser automation is the path, though it reads as background rather than behavior.

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 value — returns instructions, opens nothing, then use cotlet_browser_* — is front-loaded and clear. However, the final sentence about PhotoShelter publishing API documentation and customers contacting support for a key is tangential to invoking this tool and lengthens a zero-parameter definition. The phrasing is also run-on, stacking several clauses with semicolons.

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 burden of explaining return values and does so: a step-by-step sequence with screens, buttons, and fields. It also clarifies the tool's non-action nature and points to the follow-up tools. What is missing is any indication of scope, such as whether the guide presumes an already-selected gallery or how the guide is tailored to the user's account.

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 there is no parameter meaning for the description to add; the baseline of 4 applies. The description does not invent inputs or imply that gallery identity must be supplied, which is consistent with the empty schema.

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 action and resource ('Share gallery in the user's own PhotoShelter account') and immediately clarifies that the tool only produces instructions rather than performing the share. That distinction is essential because the name alone would suggest it executes the share. It stops short of naming the sibling that actually performs the action by name, though it gestures at the cotlet_browser_* family.

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?

Explicit when-to-use guidance is present: use this to get step-by-step instructions, then perform the action with the cotlet_browser_* tools in the PhotoShelter Cloud Browser. The key exclusion ('opens nothing by itself') prevents the common mistake of assuming this tool does the work. It does not compare against photoshelter_set_gallery_access, which covers a related sharing/access outcome.

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.