Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_greenhouse_job

Fetch a single Greenhouse job by board token and job ID to get title, company, location, URLs, compensation, and description. Returns 404 for unknown token or ID.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesGreenhouse job id
tokenYesGreenhouse board token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4/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 reasonably well: it enumerates the returned fields (title, company, department, compensation, description as HTML and plain text) and discloses the failure mode — an unknown token or id returns 404. It omits any auth or rate-limit context, but the error and payload behavior is genuinely useful.

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?

Three tightly written sentences with zero filler; identity and required inputs are front-loaded before the return payload and error behavior. Every clause carries information.

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-parameter lookup with no output schema, the description supplies the missing return-value information and the 404 behavior, which is what an agent needs to call and interpret it. The only small gap is guidance on how to obtain the token/id pair, but nothing essential to invocation is 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%, with both parameters documented in the schema, so the baseline is 3. The description restates that 'token' means the board token and 'id' the job id and that both are required, which mirrors the schema rather than adding new semantics.

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 opens with a specific verb and resource ('Get a single Greenhouse job') and immediately scopes it to one record identified by board token and job id, which distinguishes it from the sibling listing tool jobs_greenhouse_board. An agent can tell what it retrieves without opening the schema.

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 requirement that both token and id are needed implies the tool is a detail fetch that follows a board/search lookup, and returning 'one' job separates it from listing tools. However, there is no explicit when-to-use or when-not statement and no sibling (e.g. jobs_greenhouse_board) is named as the way to obtain these identifiers.

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