Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Behance profile projects

behance_profile_projects_list
Read-onlyIdempotent

Retrieve a Behance profile's most recent projects with summaries, cover images, and publish dates by username. Use it to review a creator's recent work before outreach, collaboration, or portfolio research.

Instructions

List a profile's most recent Behance projects, with summaries, cover images and publish dates. Requires username. 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": {
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "behance_profile_projects_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Profile handle, e.g. `chrisd3b8`. Handles are case-insensitive and may contain non-ASCII letters.
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 readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that results include summaries, cover images and publish dates, which is genuinely useful given no output schema, but it says nothing about pagination, limits, or ordering beyond 'most recent'.

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?

Three short sentences, front-loaded with the core action and return contents. 'Returns a list' is low-value filler since the verb already says list, but overall there is little waste.

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?

With no output schema, the description partially compensates by naming returned fields. It omits pagination and result-count behavior, which matters for a listing tool whose schema includes a conversation_id echo requirement hinting at stateful paging.

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 detailed notes on username format and case-insensitivity, so the schema carries the load. The description only repeats that username is required and adds no meaning about context, llm_model, or conversation_id handling.

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 and resource ('List a profile's ... Behance projects') and names the returned fields. However, it does not distinguish itself from the sibling behance_projects_recent_list, leaving the profile-scoped vs. global-recent distinction to inference.

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?

Usage is implied by 'a profile's most recent' plus the required username, so an agent can infer this is for per-profile browsing. There is no explicit when-to-use, when-not, or reference to any alternative such as behance_projects_recent_list or behance_profile_get.

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