Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Behance profile

behance_profile_get
Read-onlyIdempotent

Retrieve a Behance person or team profile—including stats, links, availability, tools, teams, members, and projects—by username to support portfolio research and team analysis.

Instructions

Get a Behance person or team profile with its stats, links, availability, tools, teams, members and projects. Requires username.

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

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

A3.6/5.0
Behavior3/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. The description adds genuine value beyond that by describing the shape of the returned profile (stats, links, teams, members, projects). It says nothing about failure behavior for unknown/private handles, auth needs, or rate limits, which keeps it at an adequate rather than strong level.

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, front-loaded with the verb and resource, then a compact enumeration of returned data and the one required input. No filler, no repetition, and every clause carries information.

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 read-only profile fetch with no output schema, the description compensates well by enumerating the returned fields. Annotations cover the safety profile and the schema fully documents all four parameters. The remaining gap is edge-case behavior for non-existent or private profiles, which is minor for this tool class.

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%, with context, username, llm_model and conversation_id all documented in detail including the pattern and case-insensitivity rule. The description's 'Requires `username`' merely restates what the schema already marks as required, so it adds no meaning beyond the input 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?

States a specific verb and resource ('Get a Behance person or team profile') and enumerates what the payload contains (stats, links, availability, tools, teams, members, projects). The person/team distinction is a useful scope clarification. It does not, however, explicitly contrast itself with siblings like behance_profile_projects_list or behance_project_get, even though it mentions 'projects' in its return list.

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 only implied by the tool's name and purpose; there is no explicit when-to-use or when-not-to-use statement and no named alternative for related lookups such as profile projects or individual projects. The only concrete guidance is the 'Requires `username`' prerequisite, which is minimal but does orient the caller.

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