Skip to main content
Glama
Sign In
Behance MCP Server

Behance MCP Server

by Arnonfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_behance_jobs

Retrieve job listings from Behance including job title, company, location, type, posting date, required skills, and remote availability. Filter by location and category to find relevant creative roles.

Instructions

Get job listings from Behance. Returns job title, company, location, job type, posted date, required skills, and remote availability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_behance_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category (e.g., "Graphic Design", "UI/UX", "Illustration")
locationNoFilter by location (e.g., "New York", "London", "Remote")
maxItemsNoMaximum number of jobs to return (default: 50, max: 100)

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 fully disclose behavior. It mentions returned fields but does not state if it's read-only, rate limits, pagination, or other side effects.

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 concise sentences that front-load the purpose and list key fields. No unnecessary words.

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?

No output schema, but description lists return fields. However, lacks details on filtering behavior, pagination, or error handling; adequate for a simple listing tool.

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 coverage is 100% with descriptions for all parameters. The tool description adds no additional parameter meaning beyond the schema, achieving the baseline score.

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 gets job listings from Behance and lists the specific fields returned (job title, company, etc.). It is distinct from sibling tools like get_behance_job_details or search_behance_projects.

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?

No explicit guidance on when to use this tool versus alternatives. The sibling names imply it's for listing jobs vs getting details, but the description doesn't clarify.

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