Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble service

dribbble_service_get
Read-onlyIdempotent

Retrieve Dribbble service details such as description, media, price, milestones, and owner using a serviceId to assess a specific design listing.

Instructions

Get Dribbble service details: description, media, price, milestones and owner. Requires serviceId.

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

Input Schema

NameRequiredDescriptionDefault
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.
serviceIdYesRequired. Service id as it appears in Dribbble URLs, e.g. `165194-High-Converting-Landing-Page-Design`. The numeric id alone is also accepted.
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.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so safety is covered. Because there is no output schema, the description's enumeration of returned fields (description, media, price, milestones, owner) is the only documentation of the response shape, which is meaningful added context; error behavior for unknown ids remains unstated.

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?

Two short sentences with zero filler; the payload list comes first and the required-input note second. Nothing could be removed without losing information.

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-resource read with no output schema, the description supplies the essential return-field list and the required parameter, which is what an agent needs to call it correctly. It could be more complete by noting what happens on an invalid or missing service id.

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 serviceId pattern and examples, so the schema does the heavy lifting. The description only restates that serviceId is required, adding no format or edge-case detail beyond it, which lands at the baseline.

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 names a specific verb+resource ('Get Dribbble service') and enumerates the payload ('description, media, price, milestones and owner'), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling 'dribbble_services_search', so it stops short of 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 Guidelines3/5

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

Usage is only implied: fetch a single service when you have its id. The closing 'Requires `serviceId`' establishes a precondition but not a when-to-use rule, and no alternative such as dribbble_services_search is named for the case where the id is unknown.

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