Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dribbble designers

dribbble_designers_search
Read-onlyIdempotent

Search Dribbble designers by query, category, location, rating, and work availability to find candidates matching specific hiring criteria.

Instructions

Search Dribbble designers with category, location, rating and availability filters. Optional inputs: query, category, location, minimumRating, availableForWork and 5 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_designers_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 100; a numeric string is accepted too. Defaults to 1. Cannot be combined with `cursor`. Dribbble reshuffles this list on every request, so numbered pages repeat designers; follow `page.nextCursor`.
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 designers; omit for all designers.
categoryNoDirectory category slug (`category`), e.g. `brand-designers`. An unknown slug is answered as a keyword search. A category is one page; `page` above 1 and cursors are refused, so use `query` to page.
locationNoDesigner location as text, e.g. `New York`.
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.
agenciesOnlyNoSet to `1` or `true` to return only agencies; omit for all designers.
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.
respondsQuicklyNoSet to `1` or `true` to return only designers who respond quickly; omit for all designers.
availableForWorkNoSet to `true` or `1` to return only designers marked available for work; `false` or `0` (the default) returns everyone.

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 only adds that the result is a list and that a cursor continues pagination; it does not mention the underlying goal/llm_model context parameters or the conversation_id handshake, which materially affect how the tool must be called.

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 with the resource and filters front-loaded and no filler. The phrase 'and 5 more' is a bit vague but keeps the definition compact rather than enumerating all 13 parameters.

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?

For a 13-parameter tool with two required context parameters and no output schema, the description covers the search framing and the list return shape but omits the pagination-correctness caveats and the conversation_id/context requirements. Adequate but under-specified relative to the tool's actual complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains every parameter including the page/cursor interaction and the category slug constraint. The description mirrors the filter names and adds no new semantics, but its summary of the filterable dimensions is still a useful orientation; baseline-plus is fair given the schema does the heavy lifting.

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 designers' -- plus the filter dimensions (category, location, rating, availability). That cleanly separates it from the sibling search tools for jobs, briefs, services and collections, though it never names those alternatives 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?

Implies the search use case and notes that paginated results should be continued with a cursor, but gives no explicit when-to-use / when-not-to-use guidance against siblings like dribbble_profile_get or dribbble_services_search. The real paging rules (page vs cursor, category is single-page only) live in the schema rather than the description.

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