Skip to main content
Glama
Greenhouse MCP

Greenhouse MCP

by benmonopoli

list_board_jobs

Retrieve all published jobs visible to external candidates on the public job board. Use this read-only tool to browse open roles or optionally include full job descriptions.

Instructions

List all published jobs on the public job board. Read-only.

Returns jobs visible to external candidates. For internal job data with pipeline info, use list_jobs instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_board_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoInclude full job content/description

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / content / description
      Added value: +"Include full job content/description"
  2. Addedv0.3.4

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it does disclose the read-only nature and the visibility constraint (only jobs visible to external candidates). It does not cover pagination or rate-limit behavior, but the safety-relevant disclosure is present and correct.

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?

Two short sentences, zero filler, with the public-board scope front-loaded ahead of the disambiguation note. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with an output schema covering return values, no further explanation is required. Scope, safety profile, and sibling routing are all present.

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?

Only one parameter (content) exists and schema description coverage is 100%, so the schema already documents it fully. The description adds no meaning about the content toggle, making the baseline 3 appropriate.

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?

States a specific verb (list) plus resource (published jobs) and scope (public job board), and explicitly contrasts itself with the sibling list_jobs. An agent can distinguish it without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: use this for externally visible board jobs, use list_jobs when internal pipeline data is needed. The alternative is named and the selecting condition is stated, leaving nothing 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