Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dribbble jobs

dribbble_jobs_search
Read-onlyIdempotent

Find Dribbble job listings by keyword, location, specialty, and employment type, including remote, full-time, or freelance roles.

Instructions

Search Dribbble jobs by query, location and employment type. Optional inputs: query, specialtyIds, location, anywhere, fulltime and 3 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_jobs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 100; a numeric string is accepted too. Defaults to 1. Cannot be combined with `cursor`. A page past the last is an empty list with `page.hasMore` false.
queryNoSearch text, e.g. `designer`. 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.
anywhereNoSet to `1` or `true` to return only jobs open to remote candidates; omit for all jobs.
fulltimeNoSet to `1` or `true` to return only full-time jobs; omit for all jobs.
locationNoJob 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.
specialtyIdsNoSpecialty ids, comma-separated (`1,2`) or repeated: 1 Animation, 2 Brand / Graphic Design, 3 Illustration, 4 Leadership, 5 Mobile Design, 6 UI / Visual Design, 7 Product Design, 8 UX Design / Research, 9 Web Design.
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.
freelanceOrContractNoSet to `1` or `true` to return only freelance or contract jobs; omit for all jobs.

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 the return shape ('Returns a list') and a pagination hint, but says nothing about result limits, rate limits, or that a conversation_id handshake is required before parallel calls (which lives only in the schema).

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

Conciseness3/5

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

Two short sentences, front-loaded with purpose, which is good. However the parameter enumeration is low-value and inaccurate ('and 3 more' when there are six additional parameters), so the sentence does not fully earn its place.

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 an 11-parameter read-only search with full schema coverage and no output schema, the description covers purpose, optional filtering, and list/cursor semantics. The numeric drift in the parameter count and the absent cross-tool routing are the only meaningful omissions.

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 coverage is 100%, so every parameter is already documented, including enum meanings and the page/cursor mutual exclusion. The description merely re-lists five parameter names and hand-waves the rest with 'and 3 more', adding no meaning 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?

States a specific verb (Search) and resource (Dribbble jobs) plus the three main filter axes (query, location, employment type). An agent can distinguish it from dribbble_job_get or dribbble_designers_search, though sibling differentiation is only implicit via the word 'jobs'.

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?

No statement of when to use this versus sibling searches like dribbble_briefs_search, and no prerequisites or exclusions. The only guidance is a pagination aside ('use cursor when paginated'), which is operational, not selection-oriented.

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