Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble collection

dribbble_collection_get
Read-onlyIdempotent

Fetch a Dribbble collection's details and a page of its shots, including likes and views, using the profile handle and collection ID.

Instructions

Get Dribbble collection details and a page of its shots with likes and views. Requires handle and collectionId.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "<handle>",
      "collectionId": "<collectionId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dribbble_collection_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 100; a numeric string is accepted too. Defaults to 1. Cannot be combined with `cursor`.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same operation and filters.
handleYesRequired. Dribbble profile handle, e.g. `simplebits`. Not case-sensitive.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
collectionIdYesRequired. Collection id as it appears in Dribbble URLs, e.g. `4582-Data-Viz`. The numeric id alone is also accepted.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety needs no description work. The description adds real value by disclosing the payload ('a page of its shots with likes and views'), but it omits operationally significant behavior that lives only in the schema — page/cursor mutual exclusion and the conversation_id sequencing rule against parallel calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, with the resource scope front-loaded before the parameter prerequisite. Nothing could be removed without losing information.

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?

The parameter surface is fully specified in the schema and no output schema exists, so the description's job is largely satisfied by naming the resource and the returned content. It stops short of a 5 only because the paging/cursor interaction and the conversation_id handshake are never surfaced in prose that an agent scanning descriptions would see.

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 description coverage is 100%, so every parameter is fully documented in structured data and the baseline is 3. The description only repeats that `handle` and `collectionId` are required, and says nothing about the paging model, so it adds no meaning beyond the schema.

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 uses a specific verb and resource ('Get Dribbble collection details and a page of its shots'), which immediately tells an agent this is a single-collection fetch that also returns shots, not a listing of a profile's collections. It does not explicitly name the sibling it contrasts with (e.g. dribbble_profile_collections_list), so it lands just 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 only implied by the shape of the resource ('collection details and ... its shots'), and the sentence about `handle`/`collectionId` is a prerequisite restatement rather than guidance. There is no statement of when to prefer this over the collections-list sibling or when-not to call it.

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

Deploy Server

Other Tools