Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Dribbble project briefs

dribbble_briefs_search
Read-onlyIdempotent

Search Dribbble project briefs by category, project scope, timeline, and client type to find matching design opportunities.

Instructions

Search Dribbble project briefs with category, scope, timeline and client filters. Optional inputs: categories, projectScope, timeline and clientType. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
timelineNoTimeline values, comma-separated or repeated: `timeline=few_days`, `timeline=few_weeks`, `timeline=month_or_more` or `timeline=unsure`, e.g. `timeline=few_weeks`.
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.
categoriesNoCategories, comma-separated (`branding,website design`) or repeated: logo design, branding, landing page, website design, mobile app, ui ux design, illustration, animation, icons, social media, presentation, print.
clientTypeNoClient-type values, comma-separated or repeated: `verified`, `promising` or `returning`, e.g. `clientType=verified`. The board does not apply this filter, so all client types are returned.
projectScopeNoDesign-only or development-required work: `projectScope=design_only` or `projectScope=dev_required`, e.g. `projectScope=design_only`.
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.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that the tool returns a list, without explaining pagination, result shape, or the conversation_id handshake beyond what the schema says. With annotations carrying the main behavioral burden, this is adequate but thin.

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?

The description is two short sentences, front-loads the verb and resource, and avoids unnecessary prose. Listing the optional filter names is somewhat redundant with the schema, but the text remains efficient.

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 seven-parameter search tool with no output schema, the description is sparse but the schema is fully documented and annotations cover safety. It could do more to surface operational details such as the conversation_id handshake, the ignored clientType filter, and the contrast with brief-get tools.

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 schema already defines all seven parameters, including the optional filters and their enums. The description merely names categories, projectScope, timeline, and clientType without adding meaning beyond the schema. It also omits the schema's notable caveat that clientType is not actually applied by the board.

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 uses a specific verb and resource — 'Search Dribbble project briefs' — and names the filter dimensions (category, scope, timeline, client). It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as dribbble_brief_get or behance_freelance_briefs_list.

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?

The description says the tool searches briefs with filters, but gives no explicit when-to-use guidance, no exclusions, and no named alternatives for getting a single brief or browsing Behance briefs. Usage is only faintly implied by the word 'Search'.

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