Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Dribbble profile articles

dribbble_profile_articles_list
Read-onlyIdempotent

Retrieve a Dribbble profile's published articles, including blurb, date, byline, and image, by supplying the profile handle.

Instructions

List Dribbble profile articles with blurb, date, byline and image. Requires handle. Returns a list.

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_articles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/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 useful post-call context by naming the fields returned, but says nothing about pagination, result caps, or behavior for invalid/suspended handles.

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 the primary action and the returned fields. 'Returns a list' is largely redundant for a tool whose name and verb already say it returns a collection, but the overall wording is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, listing the returned fields is genuinely helpful and partially compensates. However, for a paginated-style list endpoint the description omits result volume/ordering behavior, and it never addresses the conversation_id handshake that the schema warns about.

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 four parameters (including context, llm_model and conversation_id) are fully documented in the schema. The description only repeats 'Requires `handle`' and adds no syntax, format, or case-sensitivity detail beyond what the schema states. 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 states a specific verb and resource ('List Dribbble profile articles') and names the returned fields (blurb, date, byline, image), so an agent can tell it apart from shot/collection listing tools. It does not explicitly contrast with the nearest sibling, dribbble_profile_shots_list, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Requires `handle`', which is a prerequisite already enforced by the schema, not a when-to-use rule. Nothing says when to pick this over dribbble_stories_list or dribbble_profile_shots_list, and there are no exclusions or 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