Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_lever_postings

List a company's public Lever job postings using its careers URL slug, with optional filters for department, location, and remote status.

Instructions

List a company's Lever postings. Lists a company's public Lever postings (detail is inline), optionally filtered by department, location, or remote. The company is the Lever slug from its careers URL.

Input Schema

NameRequiredDescriptionDefault
remoteNoFilter by remote (true or false)
companyYesLever company slug (careers URL)
locationNoFilter: location contains
departmentNoFilter: department contains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that postings are "public" and that "detail is inline," which tells the agent the list response is self-contained. However, it says nothing about pagination, result limits, or completeness of the listing.

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?

The description is short and front-loads the core action. The first sentence is largely repeated by the second ("List a company's Lever postings" vs "Lists a company's public Lever postings"), a minor redundancy, but overall it is efficient.

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 filterable list tool with no annotations and no output schema, the description covers the action, the filters, and how to identify the company. It leaves return shape and pagination behavior unaddressed, which is acceptable but not fully complete.

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 the schema already documents all four parameters. The description restates the filterable fields (department, location, remote) and slightly clarifies the company parameter, but adds little beyond the schema, so 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?

The description states a specific verb and resource ("List a company's Lever postings") and names the data source (Lever), which inherently separates it from sibling boards like jobs_greenhouse_board or jobs_workable_postings. It does not explicitly name those alternatives, but the purpose is unambiguous.

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?

Usage is implied rather than stated: it tells the agent to list postings for a Lever-based company and how to obtain the company value ("the Lever slug from its careers URL"). There is no explicit when-to-use versus when-not-to-use guidance or named alternative tools.

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