Skip to main content
Glama
Casius999

decroche-mcp

by Casius999

source_lever

Retrieve published job postings from a Lever company page by providing the company slug, without authentication.

Instructions

Fetch all published postings from a Lever company page (no auth required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyYesThe Lever company slug (e.g. ``"techstart"``).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYes
queryNo
countYes
jobsNo
warningsNo
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses no auth requirement, which is useful. Lacks details on rate limits, pagination, or side effects, but acceptable for a simple read operation.

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?

Single sentence with all key information front-loaded. No wasted 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?

Given one parameter, clear purpose, and existence of output schema, description is complete. Could mention if pagination is needed, but 'all published postings' suggests no further filtering.

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%, so baseline is 3. Description adds minimal context ('company page') but doesn't deepen meaning beyond schema. Adequate.

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 fetches all published postings from a Lever company page, using specific verb and resource. It distinguishes itself from sibling source tools by naming Lever explicitly.

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 mentions 'no auth required' but does not provide explicit guidance on when to use this vs. alternatives. Context implies it's for Lever pages, but no exclusions or alternative tool names given.

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