Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dribbble profile shots

dribbble_profile_shots_list
Read-onlyIdempotent

List a Dribbble profile's shots, sorted by newest or popular, with likes, views and dates. Provide a handle to retrieve paginated results using a cursor.

Instructions

List Dribbble profile shots, newest or popular, with likes, views and dates. 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_shots_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 100; a numeric string is accepted too. Defaults to 1. Cannot be combined with `cursor`.
sortNo`recent` (default; pinned first, then newest) or `popular` (Dribbble's own popularity order).
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.5/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 the safety profile is covered. The description adds the hard requirement of `handle` and the pagination cue, which is useful, but says nothing about rate limits, error behavior, or what happens with an invalid/expired cursor.

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 short sentences, front-loaded with what the tool returns followed by the prerequisite and pagination note. No filler, though 'Returns a list' is mildly redundant with 'List' in the opening clause.

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 read-only listing tool with seven fully documented parameters and no output schema, the description covers purpose, required input, and pagination adequately. The mention of likes/views/dates gives a hint of the payload without needing a full return-value spec.

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 page, sort, cursor, handle, context, llm_model and conversation_id are all documented in the schema itself. The description only restates the `handle` requirement and cursor usage; it adds no meaning beyond the schema, which is the expected baseline of 3.

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?

Uses a specific verb+resource ('List Dribbble profile shots') and adds sort semantics ('newest or popular') plus the kind of data returned ('likes, views and dates'). It does not explicitly differentiate itself from the many sibling *_list tools, but the resource name is specific enough that an agent can identify it.

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?

Gives one piece of procedural guidance: 'use cursor when paginated.' It never says when to use this tool versus alternatives such as dribbble_profile_get or the other profile sub-list tools, so selection guidance is only implied by the resource name.

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