Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble story

dribbble_story_get
Read-onlyIdempotent

Retrieve Dribbble story details—body, author, category, and view count—by providing the required story slug.

Instructions

Get Dribbble story details with body, author, category and view count. Requires slug.

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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "dribbble_story_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Story path, e.g. `2026/10/31/ai-and-robotics-branding`, as returned in the stories list.
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by naming the returned content (body, author, category, view count), which matters since there is no output schema, but it says nothing about the required `context`/`llm_model`/`conversation_id` analytics contract or any rate/error behavior.

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 the action and return fields, with no wasted wording. It could be tightened only by dropping the redundant "Requires `slug`", which the schema already marks required.

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 single-record read tool with a fully described four-parameter schema, the definition covers which resource is fetched and what fields come back, compensating for the absent output schema. The main missing piece is routing guidance relative to dribbble_stories_list and the sibling *story_get tools.

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 slug format (path pattern, example), context, llm_model and conversation_id are all fully documented in the schema itself. The description only restates that slug is required, adding no new meaning beyond it; 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 (Get) and resource (Dribbble story) and enumerates what the result contains: body, author, category and view count. That is enough to tell it apart from dribbble_stories_list, which is inferred as the listing counterpart, though the description never names that sibling 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?

The sentence "Requires `slug`" plus the schema note that the slug comes "as returned in the stories list" implies the workflow: list stories first, then fetch one by slug. There is no explicit when-to-use/when-not guidance or named alternative, 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