Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_lever_posting

Retrieve a specific Lever job posting by company slug and posting ID, returning title, department, location, compensation, URLs, and full description.

Instructions

Get a single Lever posting. Returns one Lever posting, identified by the company slug and posting id, both required. The response has the title, department, team, location, workplace type, employment type, posting and apply URLs, posting date, compensation, and the description as HTML and plain text. An unknown company or id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesLever posting id
companyYesLever company slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a real edge behavior (404 on unknown company or id). It also enumerates the response payload in detail, giving the agent confidence about what comes back, though it omits auth/rate-limit notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action, and the response-field enumeration earns its place since no output schema exists. The field list is dense but not padded; nothing is redundant.

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 two-param single-item lookup with no output schema and no annotations, the description covers what it does, both required inputs, the error case, and the full return shape. Only minor behavioral notes (auth, rate limits) are absent.

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 description coverage is 100%, so both `company` and `id` are already documented as slug and posting id. The description restates that both are required but adds no format, example, or derivation guidance beyond the schema, so the baseline 3 applies.

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?

"Get a single Lever posting" states a specific verb (get) and resource (Lever posting), and "single" scopes it against the list-oriented sibling jobs_lever_postings. It does not name that sibling explicitly, so the discrimination is implied rather than stated.

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 establishes that both identifiers are required and that an unknown company/id returns 404, which is useful implicit guidance on inputs. However it never says when to reach for this tool versus jobs_lever_postings or other ATS job tools, and no exclusion or alternative is given.

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