Skip to main content
Glama
Sign In
Behance MCP Server

Behance MCP Server

by Arnonfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_behance_profile_details

Get detailed Behance user profile data including bio, company, occupation, social links, and complete stats by providing a profile URL.

Instructions

Get detailed information about a specific Behance user profile including bio, company, occupation, social links, and complete stats.

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": {
      "profileUrl": "<profileUrl>"
    },
    "name": "get_behance_profile_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileUrlYesFull URL of the Behance profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It mentions the type of data returned but does not state whether the operation is read-only, requires authentication, or how it handles errors (e.g., invalid URL, non-existent profile).

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?

A single, well-structured sentence that front-loads the purpose and lists key information included. No redundant words; every part earns its place.

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 tool with one parameter and no output schema, the description is adequate but incomplete. It covers what data is returned but omits behavioral context (e.g., read-only nature, error handling, or typical response structure).

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%; the parameter description ('Full URL of the Behance profile') is clear and matches the tool's purpose. The tool description adds no additional meaning beyond the schema, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves detailed information about a specific Behance user profile, listing key fields like bio, company, occupation, social links, and stats. This distinguishes it from siblings like get_behance_project_details (different resource) and search_behance_profiles (search vs. retrieval).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., search_behance_profiles). The description implies use when you have a profile URL, but does not state prerequisites or contrast with sibling tools.

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