Skip to main content
Glama

dribbble_guide

Provides guidance for navigating Dribbble workflows, including leads, client messages, Pro Analytics, shots, and comments, and returns the sign-in link. Use it first to plan tasks.

Instructions

How to work in Dribbble (leads, client messages, Pro Analytics, shots and comments): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Dribbble, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the topical scope and that a sign-in link is included, implying a safe read. However, it says nothing about the return shape (prose vs. structured steps), whether the guide is static or context-sensitive to the task argument, or what happens with an empty task.

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?

Two sentences, front-loaded with the resource and scope, ending with the actionable 'Call this first.' The parenthetical list and slightly awkward 'its screens and the sign-in link' clause cost a little crispness but nothing is padded.

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 one-optional-parameter guide tool with no output schema, the description gives enough scope for an agent to know what content it will receive and to call it before acting. The only gap is not knowing whether the response adapts to the task argument.

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?

Schema coverage is 100% and the single optional 'task' parameter is already documented as 'What you want done in Dribbble, in your words.' The description adds no further meaning, such as whether the task string narrows which guide sections are returned. Baseline 3 applies.

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 (Dribbble) and enumerates the domains the guide covers: leads, client messages, Pro Analytics, shots, comments, plus screens and the sign-in link. It is clearly a documentation/onboarding tool, distinct from the action siblings (open, click, type, read, status, close). The verb is implicit ('How to work in...') rather than a crisp action, which keeps 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?

'Call this first' gives explicit sequencing guidance that no sibling name conveys on its own. There is no statement of when NOT to use it (e.g., after onboarding, go straight to dribbble_open), so it falls short of full when/when-not coverage.

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