Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dribbble stories

dribbble_stories_list
Read-onlyIdempotent

List Dribbble stories with titles, dates, teasers, and images; filter by category and paginate using page numbers or cursors.

Instructions

List Dribbble stories with title, date, teaser and image. Optional inputs: category, page and cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dribbble_stories_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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoStory category slug (`category`), one of community, hang-time, inspiration, interviews, meetups, podcast, process, updates. An unknown slug is not_found.
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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds the return shape and a pagination hint, but omits other behavior an agent would care about — notably that page and cursor are mutually exclusive and that a conversation_id handshake exists.

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 purpose and return fields, then inputs, then the pagination note. No filler, though the trailing parenthetical is slightly redundant with the schema's cursor description.

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?

With no output schema, the description usefully names the fields returned and signals pagination, which is the main missing structured information. It does not cover the `context`/`llm_model`/`conversation_id` protocol parameters, but those are fully explained in the schema, so a 4 is appropriate for a simple list operation.

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%, so every parameter (including the enum-like category slugs, the page range, and the cursor provenance rule) is already documented in the schema. The description merely restates the three optional parameter names without adding format or interaction details, so the 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?

"List Dribbble stories" is a specific verb+resource, and the description enumerates the returned fields (title, date, teaser, image). It does not explicitly distinguish itself from the sibling `dribbble_story_get`, but the list-vs-single distinction is strongly implied by the verb.

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?

It names the optional filters and gives one piece of operational guidance ("use cursor when paginated"). It never states when to prefer this over `dribbble_story_get` or when a category filter is appropriate, so usage is only implied.

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