Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dribbble services

dribbble_services_search
Read-onlyIdempotent

Search Dribbble service listings by query, category, budget, location, rating, delivery time, and seller type to shortlist designers or agencies for your project.

Instructions

Search Dribbble services with category, budget, location and rating filters. Optional inputs: query, categories, budgetMin, budgetMax, location and 8 more. 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_services_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 42; a numeric string is accepted too. Defaults to 1. Cannot be combined with `cursor`.
queryNoSearch text, e.g. `logo`. Up to 200 characters.
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.
proOnlyNoSet to `1` or `true` to return only Pro sellers; omit for all sellers.
durationNoDelivery time (`duration`): `P3D` (under 3 days), `P1W` (under a week) or `P1M` (under a month). `3d`, `1w` and `1m` are accepted too.
locationNoDesigner location as text, e.g. `New York`.
budgetMaxNoMaximum budget in whole US dollars, e.g. `5000`. Must be at least `budgetMin`.
budgetMinNoMinimum budget in whole US dollars, e.g. `1000`. Must not exceed `budgetMax`.
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.
categoriesNoCategory labels, comma-separated or repeated: Branding, Web Design, Illustration, App & Product Design, Animation & Motion Graphics, Typography, Print Design.
agenciesOnlyNoSet to `1` or `true` to return only agencies; omit for all sellers.
minimumRatingNoMinimum rating in whole stars from 0 to 5, e.g. `4`. Any value, including `0`, limits results to entries that have a rating.
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.
instantCheckoutNoSet to `1` or `true` to return only services with instant checkout; omit for all services.
respondsQuicklyNoSet to `1` or `true` to return only sellers who respond quickly; omit for all sellers.

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 readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds that results are a list and that a cursor is the continuation mechanism, which is genuinely useful beyond the annotations, but it says nothing about result volume, rate limits, or the conversation_id sequencing handshake the schema hints at.

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 the resource and main filters, with the return/pagination note second. "and 8 more" is a slightly lazy shorthand, but nothing is padded or redundant.

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 16 parameters, two required non-search parameters (context, llm_model) and no output schema, the description carries a fair burden and covers the return shape adequately. It omits any mention of the required context/llm_model inputs or the conversation_id continuation rule, which are the least obvious parts of calling this tool correctly.

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 the baseline is 3; every parameter is already documented in the schema with examples and constraints. The description only restates four filter names and waves at "8 more" by count, adding no meaning beyond what the schema provides.

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 and resource ("Search Dribbble services") and enumerates the primary filter dimensions (category, budget, location, rating), so an agent knows exactly what the tool returns. It does not distinguish itself from near siblings such as dribbble_designers_search or dribbble_profile_services_list, so it stops short of 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 when-to-use or when-not-to-use guidance and no mention of alternatives, even though designers, briefs, jobs and profile-service listings all sit in the sibling set. The only operational hint is "use cursor when paginated", which is pagination mechanics, not routing guidance.

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