Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Behance project

behance_project_get
Read-onlyIdempotent

Retrieve a Behance project's details by project ID, including its name, URL, owners, cover images, color, and downloadable source files.

Instructions

Get a Behance project's id, name, URL, owners, covers, colour and downloadable source files. Requires projectId.

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

Input Schema

NameRequiredDescriptionDefault
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.
projectIdYesRequired. Project id, e.g. `77359879`.
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

A3.9/5.0
Behavior4/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 structurally. The description adds genuine value that annotations do not: it discloses what content comes back, notably downloadable source files and covers. It says nothing about auth, rate limits, or missing/deleted projects, so it is not a 5.

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 sentences, both earning their place: the first front-loads what is returned, the second front-loads the hard requirement. No filler, no restating of the title beyond the necessary resource name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the returned fields, which is exactly what an agent needs to decide whether this tool answers the question. The three metadata parameters are fully explained in the schema, so nothing needed for correct invocation is missing.

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 all four parameters (projectId, context, llm_model, conversation_id) are already documented in the schema, including the example id format. The description only restates that projectId is required, adding no syntax, range, or behavioral detail beyond the structured fields. 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 ('Get') and resource ('Behance project'), then enumerates the returned fields (id, name, URL, owners, covers, colour, downloadable source files), which makes it clearly distinguishable from behance_profile_get or behance_tag_get. It stops short of naming a sibling or scope constraint, so it is a clear 4 rather than 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?

The line 'Requires `projectId`' implies this is a single-project lookup keyed by id, giving implicit usage guidance. However, it never says when to prefer this over sibling lookups (e.g. project lists vs. project detail) or what to do when only a URL/slug is known; there are no explicit exclusions.

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