Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dribbble profile collections

dribbble_profile_collections_list
Read-onlyIdempotent

List a Dribbble user's profile collections to retrieve shot and designer counts plus cover images for each collection. Provide the profile handle and use pagination cursors for multi-page results.

Instructions

List Dribbble profile collections with shot and designer counts and cover images. Requires handle. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dribbble_profile_collections_list"
  }
}

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.
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds meaningful context beyond that: what the records contain (shot and designer counts and cover images) and that cursor pagination applies. It stops short of describing the response shape or page-size behavior, but for a read-only list that is a modest gap.

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?

Three short sentences, front-loaded with purpose and returned fields before prerequisites and pagination. The "Requires `handle`" sentence partly duplicates the schema's required list, which is the only wasted motion.

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?

There is no output schema, so the description usefully fills in what comes back (collections with counts and cover images) and flags pagination. Combined with 100% schema coverage and read-only annotations, an agent has enough to call it correctly, though response structure and pagination limits remain unspecified.

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 all six parameters (including page/cursor mutual exclusion and the context/llm_model/conversation_id conventions) are already documented in the schema. The description only restates that `handle` is required and hints at cursor usage, adding little beyond the structured fields. 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 a specific verb and resource ("List Dribbble profile collections") and adds the notable returned fields (shot/designer counts, cover images). It does not distinguish itself explicitly from nearby siblings such as dribbble_profile_shots_list or dribbble_collection_get, but the resource noun is unambiguous.

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: the tool is for fetching a profile's collections, and the `handle` prerequisite is stated. There is no explicit when-to-use versus alternatives guidance (e.g. when to use this instead of dribbble_collection_get or dribbble_profile_get), and no when-not conditions.

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