Skip to main content
Glama
Sign In
Behance MCP Server

Behance MCP Server

by Arnonfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_behance_projects

Search Behance for projects by keyword. Returns project details, creator info, and engagement stats.

Instructions

Search for projects on Behance by keyword. Returns project ID, title, URL, creator info, thumbnails, stats (views, appreciations, comments), and creative fields.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_behance_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch keyword (e.g., "graphic design", "branding", "illustration")
maxItemsNoMaximum number of projects to return (default: 50, max: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It lists return fields but omits important traits such as rate limits, pagination behavior, default sorting, case sensitivity, or maximum result count beyond the maxItems parameter. This leaves significant gaps for an AI agent to infer safe and correct usage.

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?

The description is a single concise sentence that efficiently communicates the tool's purpose and output. No redundant or unnecessary information is present.

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?

Given the absence of an output schema, the description helpfully enumerates return fields. However, it lacks details on pagination, sorting, error handling, and behavioral context (e.g., default limits, rate limiting). With only two parameters and full schema coverage, the description is partially complete but inadequate for a search tool in a production setting.

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?

Input schema coverage is 100% with both parameters having descriptions. The tool description does not add any extra semantic detail beyond what the schema already provides. Baseline score of 3 is appropriate.

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 verb ('Search'), resource ('projects on Behance'), and mechanism ('by keyword'). It also lists specific return fields, effectively distinguishing it from sibling tools that target jobs, profiles, or specific project details.

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 description implies usage for keyword-based project searches but does not explicitly state when to use this tool over alternatives like get_behance_project_details (for a specific project) or search_behance_images. No when-not-to-use guidance is provided.

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