Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble profile

dribbble_profile_get
Read-onlyIdempotent

Retrieve a Dribbble user's profile details, including identity, follower and project counts, skills, teams, and contact links, by passing their handle.

Instructions

Get Dribbble profile details: identity, counts, skills, teams and contact links. Requires handle.

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

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.4/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 fully covered without the description. The description adds useful context about what comes back (identity, counts, skills, teams, contact links), but says nothing about rate limits, auth needs, or behavior for a nonexistent handle.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that front-loads the verb, resource, and the returned field categories, with a trailing note on the required parameter. No filler or redundancy.

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, listing the returned field groups is valuable and sufficient for a simple read-only profile lookup, and the handle requirement is stated. Minor gaps remain around not-found handling and the conversation_id sequencing protocol, though the latter is documented in the schema.

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%, including the handle pattern and case-insensitivity plus the purpose of context, llm_model, and conversation_id, so the schema carries parameter meaning. The description only restates that `handle` is required, adding no syntax or format detail beyond the schema; 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 ("Get Dribbble profile details") and enumerates the payload contents (identity, counts, skills, teams, contact links), which lets an agent distinguish the base profile lookup from sub-resource siblings like dribbble_profile_shots_list or dribbble_profile_reviews_get. It stops short of explicitly naming any sibling as the alternative, so a 4 rather than a 5.

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?

There is no guidance on when to call this versus the many sibling profile/sub-resource tools, nor any exclusion or prerequisite beyond "Requires `handle`." The intended usage (fetch a designer's core profile by handle) is only inferable from the name and field list.

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