Skip to main content
Glama
Casius999

decroche-mcp

by Casius999

source_careerjet

Fetch job listings from Careerjet's international job aggregator using keywords and location filters. Specify locale to target specific markets.

Instructions

Fetch jobs from Careerjet public API (international job aggregator).

Optional env: CAREERJET_AFFID — affiliate ID for higher rate limits. Works without it in some locales (reduced results possible).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYesSearch keywords (e.g. ``"développeur python"``).
locationNoLocation filter (e.g. ``"Paris"``). Empty = all.
localeNoCareerjet locale code, default ``"fr_FR"``.fr_FR

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYes
queryNo
countYes
jobsNo
warningsNo
Behavior2/5

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

No annotations are provided, and the description only discloses that results may be reduced without the affiiliate ID. It does not state read-only nature, error behavior, 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 efficient sentences: the first defines the purpose, the second provides practical optional configuration. No unnecessary words.

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?

The description covers the essential info: source, optional rate-limit enhancement, and locale dependency. With an output schema present, it is reasonably complete, though pagination or error handling might be missing.

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 clear descriptions for all parameters. The tool description adds no additional parameter meaning, meeting the baseline for high coverage.

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

Purpose4/5

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

The description clearly states the action (fetch jobs) and resource (Careerjet public API), with the qualifier 'international job aggregator' adding context. However, it does not differentiate this source from sibling source tools beyond the name.

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?

Provides guidance on the optional environment variable for higher rate limits but no explicit advice on when to use this tool over other job source tools. The agent lacks comparative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Casius999/decroche-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server