Skip to main content
Glama

dribbble_read

Read the current Dribbble page's text along with its numbered buttons, links, and fields; optionally limit reading to a single element to inspect specific page content.

Instructions

Read the current Dribbble page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the returned content, but says nothing about whether it reflects the whole page or just the visible viewport, whether output is truncated for long pages, how the numbering is assigned, or that the call is non-mutating and safe to repeat.

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?

One tight sentence with the verb and resource front-loaded and zero filler. The colon-delimited list of returned artifacts is efficient, though the sentence stops short of any operational detail an agent would want.

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 simple single-parameter read tool with a fully documented schema and no output schema, it covers the essentials. It falls short on the behaviors an agent must know to use the result correctly, namely whether element numbering is global or page-relative and whether the snapshot is truncated.

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 "element" parameter is documented in-schema as "Read only inside this element." The description adds nothing about scoping, so the schema does all the work; 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?

States a specific verb ("Read") and a specific resource ("the current Dribbble page"), then enumerates what is returned: text and numbered buttons, links and fields. That enumeration implicitly separates it from dribbble_click and dribbble_type, which consume the numbering, though no sibling is named explicitly.

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 only implied: a read/snapshot operation that an agent would naturally call before clicking or typing. There is no statement of when to prefer it, when not to, or what to do if the needed control is not on the current page.

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