Dribbble MCP Server and API by Cotlet

List shots in Dribbble

dribbble_list_shots

Read-onlyIdempotent

List shots in the user's own Dribbble account from ChatGPT, Claude or any AI agent. Returns how to do it in Dribbble step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Dribbble Cloud Browser. Dribbble's official API: Dribbble has a public API v2, but it covers only your own profile, shots, attachments, projects and job listings (checked 11 Oct 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": "dribbble_list_shots"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations' read-only, idempotent, closed-world, and non-destructive profile, the description states the tool only returns a step-by-step procedure and opens nothing itself. That tells the agent there are no side effects and that execution must be delegated to cotlet_browser_* tools. It also discloses the official API's scope limits, which explains the tool's existence.

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?

The description is short and organized into purpose, execution path, and API context. The phrase 'from ChatGPT, Claude or any AI agent' adds little, and the leading 'List shots' wording delays the key clarification that no listing occurs, so it is not maximally crisp.

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 guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields) and what the agent must do next (cotlet_browser_* tools). It could specify the response format more explicitly, but nothing critical for invocation is missing.

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?

There are no input parameters, so there is no parameter meaning for the description to add beyond the schema. The zero-parameter baseline is 4, and the description appropriately focuses on behavior rather than argument semantics.

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 the resource (shots in the user's own Dribbble account) and clarifies that the actual operation is returning step-by-step instructions rather than performing the listing. It also names the cotlet_browser_* tools as the execution path, which distinguishes it from sibling browser tools. The leading 'List shots' phrasing is slightly misleading because the tool does not itself list shots, keeping it from a 5.

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 tells the agent to call this tool for the step sequence and then use cotlet_browser_* tools in the user's Dribbble Cloud Browser to perform the action. The official API note explains why the API is not the path for this operation. It does not state explicit exclusions against other dribbble_* siblings, so it falls short of a 5.

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

All Dribbble MCP Server and API by Cotlet tools Inspect

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

Need Help?