Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_greenhouse_board

List a company's public Greenhouse job postings by careers URL slug; set content=true to include each job's full HTML description.

Instructions

List a company's Greenhouse job board. Lists a company's public Greenhouse board postings in the shared Job shape. Set content=true to include each job's full HTML description in one call. The token is the company's Greenhouse board slug from its careers URL.

Input Schema

NameRequiredDescriptionDefault
tokenYesGreenhouse board token (careers URL slug)
contentNoInclude full HTML description per job

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.7/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 burden. It discloses that postings are public and returned in a shared Job shape, and that content=true expands payloads with full HTML, which is genuinely useful. It does not mention auth requirements, rate limits, pagination, or what happens when a token is invalid.

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?

Front-loaded with the core purpose and four compact sentences. The first two sentences overlap ('List a company's Greenhouse job board' vs 'Lists a company's public Greenhouse board postings'), a small redundancy, but overall it is tight and well ordered.

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 simple two-parameter read tool with no output schema and no annotations, the description covers purpose, the required token's origin, and the effect of the optional flag. Only minor gaps remain (pagination/auth/error behavior), which are not essential to calling it correctly.

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 parameters are already documented. The description largely restates the schema (board slug from careers URL, content=true for full HTML), adding only the 'in one call' framing, so it neither compensates for nor exceeds the structured data.

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 states a specific verb and resource ('List a company's Greenhouse job board') and clarifies the scope as 'public Greenhouse board postings in the shared Job shape.' This clearly distinguishes it from the sibling jobs_greenhouse_job (single detail) and other job-board tools.

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?

It explains the content=true option for pulling full HTML descriptions in one call, which is useful operational guidance. However, it never says when to use this board tool versus the single-job sibling (jobs_greenhouse_job) or other board tools, leaving the choice to inference.

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