Skip to main content
Glama
Sign In
Behance MCP Server

Behance MCP Server

by Arnonfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_behance_images

Search Behance images by keyword to retrieve image URLs, dimensions, and associated project and creator details.

Instructions

Search for images on Behance by keyword. Returns image URLs with dimensions, associated project info, and creator details.

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

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch keyword (e.g., "logo design", "3d render", "photography")
maxItemsNoMaximum number of images to return (default: 50, max: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It states the return type but does not mention how results are sorted, whether pagination is used, or any rate limits. The behavior is adequately described for a search tool.

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 two sentences covering purpose and return content without any wasted words. It is front-loaded and efficient.

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 simple search tool with two parameters and no output schema, the description covers the main aspects: what it searches and what it returns. It could mention sorting or limitations, but overall it is sufficiently complete.

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?

The input schema already describes both parameters with clear descriptions. The description adds no additional meaning beyond 'Search by keyword' and the schema's descriptions. With 100% schema coverage, baseline 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 tool searches for images on Behance by keyword, and specifies the return includes URLs, dimensions, project info, and creator details. This distinguishes it from sibling tools that search for jobs, profiles, or projects.

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?

The description gives no guidance on when to use this tool versus alternatives like search_behance_projects or search_behance_profiles. There is no mention of prerequisites or contexts where it is not appropriate.

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