Skip to main content
Glama
Sign In
Behance MCP Server

Behance MCP Server

by Arnonfr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_behance_job_details

Retrieve detailed information for any Behance job listing, including full job description and salary data, using the job URL.

Instructions

Get detailed information about a specific Behance job listing including full description and salary info.

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": {
      "jobUrl": "<jobUrl>"
    },
    "name": "get_behance_job_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobUrlYesFull URL of the Behance job listing

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 carries the full burden. It only mentions that the tool returns 'detailed information including full description and salary info', but does not disclose if it is read-only, authentication requirements, rate limits, or behavior on errors. Minimal disclosure beyond the tool's name.

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, front-loaded sentence that conveys the main purpose efficiently. No wasted 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?

For a simple tool with one parameter and no output schema, the description is minimally adequate but lacks details on return format, error handling, or what exactly constitutes 'detailed information'. It does not compensate for the absence of annotations.

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%: the only parameter 'jobUrl' is described as 'Full URL of the Behance job listing'. The description adds no additional meaning or context beyond what the schema already provides, so 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?

Description clearly states it retrieves detailed information (full description and salary) for a specific Behance job listing. It uses a specific verb ('Get detailed information') and resource ('Behance job listing'), and distinguishes from sibling tools like get_behance_jobs which likely list jobs.

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 when a specific job URL is available, but does not explicitly state when to use or not use this tool, or mention alternatives like get_behance_jobs for listing jobs. Guidance is implied rather than explicit.

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