Skip to main content
Glama
Sign In

ShootProof MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create gallery in ShootProof

shootproof_create_gallery
Read-onlyIdempotent

Create gallery in the user's own ShootProof account from ChatGPT, Claude or any AI agent. Returns how to do it in ShootProof step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ShootProof Cloud Browser. ShootProof's official API: ShootProof has a documented OAuth API that is free with an account, but you get a client ID only by emailing ShootProof support with your app details (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": "shootproof_create_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?

The annotations already indicate read-only and non-destructive behavior. The description adds that it 'opens nothing by itself' and returns step-by-step instructions, reinforcing the non-mutating nature. It also notes the API limitation (client ID via support email), providing useful context about why this tool exists.

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 description is somewhat verbose and buries the key clarification (that it returns instructions) after an initial sentence that suggests direct creation. The final paragraph about ShootProof's API is informative but tangential, reducing front-loading and conciseness.

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 tool with no output schema, the description adequately explains what the tool returns (step-by-step instructions) and how to proceed (use browser tools). It could be more explicit about the format of the returned instructions, but overall it is complete enough for an agent to understand its role.

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?

With zero parameters and 100% schema coverage (empty schema), there are no parameters to document. The baseline for zero params is 4.

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 specifies that the tool returns step-by-step instructions for creating a gallery in ShootProof, distinguishing it from actual creation. However, the opening 'Create gallery' phrasing may momentarily mislead, and it does not explicitly differentiate from other ShootProof tools like shootproof_share_gallery.

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 clearly states the workflow: use this tool to get instructions, then use the cotlet_browser_* tools to perform the actions. It does not provide explicit when-not-to-use guidance or compare to alternative ShootProof tools, but the usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ShootProof MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources