Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble project brief

dribbble_brief_get
Read-onlyIdempotent

Fetch a Dribbble project brief by ID to retrieve budget, timeline, description, and client verification details for evaluating design opportunities.

Instructions

Get Dribbble project brief details: budget, timeline, description and client checks. Requires briefId.

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

Input Schema

NameRequiredDescriptionDefault
briefIdYesRequired. Brief id, e.g. `160006`: up to 12 digits, optionally followed by `-` and a slug.
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.
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.4/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 that the payload includes budget, timeline, description and 'client checks', which hints at content and external data, but it says nothing about rate limits, freshness or failure modes for a missing brief.

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; the returned fields are front-loaded and the required identifier follows immediately. No filler or redundancy beyond the one repeated requirement.

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-record read tool with full schema coverage and no output schema, the description supplies the shape of the response (budget, timeline, description, client checks). Missing only how to obtain a brief id (via the search sibling) and any error behavior.

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 id pattern and the purpose of `context`, `llm_model` and `conversation_id`, so the baseline is 3. The description only restates that `briefId` is required, which the schema already marks as required.

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 ('Get Dribbble project brief details') and names the fields returned (budget, timeline, description, client checks), which tells an agent what a brief is. It does not explicitly distinguish itself from the sibling dribbble_briefs_search, so it falls 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 Guidelines2/5

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

It states 'Requires `briefId`', but that is already in the required schema. The description never says when to use it instead of dribbble_briefs_search (to find an id first), nor warns that any sibling exists. Guidance is only implied by the get-by-id shape.

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