Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Dribbble job posting

dribbble_job_get
Read-onlyIdempotent

Retrieve Dribbble job details by ID, including description, company, and posting dates, for job research and application planning.

Instructions

Get Dribbble job details with description, company and dates. Requires jobId.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesRequired. Job id as it appears in Dribbble URLs, e.g. `183719-Graphic-Designer`. The numeric id alone is also accepted.
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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds the shape of the payload (description, company, dates), which is useful because there is no output schema, but it says nothing about not-found behavior or error surfacing.

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, front-loaded with the most useful information (what you get back). The trailing "Requires `jobId`" partially duplicates the schema's own required field, so it is not entirely waste-free.

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 simple by-id read this covers the core of what an agent needs, but with no output schema the description could say more about the response shape, and it is silent on the three meta-parameters and on failure modes. Adequate but with clear gaps.

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 the schema itself documents jobId format, the context/llm_model analytics params, and conversation_id semantics in full. The description only restates that jobId is required, adding no syntax or 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?

Names a specific verb and resource ("Get Dribbble job details") and enumerates what it returns (description, company, dates), which separates it from the search sibling (dribbble_jobs_search). It never names an alternative explicitly, 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 Guidelines3/5

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

Says "Requires `jobId`", which implies a lookup-by-id usage mode rather than a search, but gives no when-to-use/when-not guidance and does not point at dribbble_jobs_search for discovery. Usage is only implied.

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