Skip to main content
Glama

dribbble_open

Opens a Dribbble page in your signed-in Cloud Browser so you can manage leads, client messages, Pro Analytics, shots, and comments.

Instructions

Open a Dribbble page in your signed-in Cloud Browser (default https://dribbble.com) to work with leads, client messages, Pro Analytics, shots and comments.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://dribbble.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that the browser is already signed in (an authenticated session) and supplies the default URL, but it does not say whether this navigates an existing tab or opens a new one, whether page content is returned (relevant given the sibling dribbble_read), or what happens on an invalid/blocked URL.

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?

A single front-loaded sentence leads with the verb and resource, then the environment and default. It is efficient, though the parenthetical default partially duplicates the schema description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter tool with no output schema and no annotations, the description covers the essentials (what it does, the environment, the default). It leaves material gaps for a browser-driving tool: session state effects, whether content is returned to the agent, and failure behaviour.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single optional parameter with 100% schema description coverage, so the schema already documents the URL and its default. The description restates the default URL but adds no format, validation or path guidance beyond what the schema provides, making the baseline of 3 correct.

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 ('Open a Dribbble page') plus the execution environment ('signed-in Cloud Browser'), which is enough to distinguish it from siblings like dribbble_read, dribbble_click and dribbble_type. It does not explicitly name those siblings, so it stops short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent can infer this is the entry point before reading, clicking or typing on Dribbble, and the mention of 'leads, client messages, Pro Analytics, shots and comments' hints at the tasks it enables. There is no explicit when-to-use/when-not or named alternative such as dribbble_read for content retrieval.

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