open-greenhouse-mcp

list_jobs

Resolve job titles to Greenhouse job IDs by listing jobs with filters for status, department, or office. Use when a user names a job to retrieve the matching ID.

Instructions

List all jobs with optional filters. Read-only.

This is the primary tool for resolving job titles to job IDs. When a user mentions a job by name ("Backend Engineer"), use this to find the matching job_id. Filter by status ('open'/'closed'/'draft'), department_id (list_departments), or office_id (list_offices). For pipeline views, use pipeline_summary with the job_id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cursor`	No	Opaque cursor from a previous call's `next_cursor`, to fetch the next page. When set, all other filters are ignored — they are already baked into the cursor.
`status`	No	Filter by status: 'open', 'closed', or 'draft'
`paginate`	No	'single' for one page, 'all' to auto-fetch every page	single
`per_page`	No	Results per page (max 500)
`office_id`	No	Filter to jobs in this office
`created_after`	No	ISO 8601 datetime — only jobs created after this
`department_id`	No	Filter to jobs in this department
`created_before`	No	ISO 8601 datetime — only jobs created before this

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Sep 2, 2026

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque cursor from a previous call's `next_cursor`, to fetch the next page. When set, all other filters are ignored — they are already baked into the cursor.",
+  "title": "Cursor"
+}

removedInput schema / properties / page

Removed value: -{
-  "default": 1,
-  "description": "Page number (starts at 1)",
-  "title": "Page",
-  "type": "integer"
-}

First observedv0.5.0Aug 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations supplied, the description carries the safety burden and it does so by explicitly labeling the tool 'Read-only.' It also states the scope ('all jobs with optional filters') and the job-ID-resolution behavior. It does not describe pagination side effects in prose, but the input schema already documents cursor and paginate behavior.

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?

Four short sentences, front-loaded with the core action and read-only nature, then the use case, filters, and alternative. Every sentence contributes information; no filler.

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 an 8-parameter filtered list tool, the description covers what it does, when to use it, how to find job IDs, what filters matter, and which sibling covers pipeline views. Pagination and return-value details live in the schema and output schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by naming the primary job-title-to-ID use case and pointing to list_departments and list_offices as sources for filter values, plus enumerating the status choices. This is useful parameter guidance not fully present in the schema.

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?

Description opens with a specific verb and resource ('List all jobs') and immediately states a clear retrieval use case: resolving job titles to job IDs. It also points to a sibling alternative (pipeline_summary), so an agent can distinguish this tool from nearby list/detail tools.

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?

The description gives explicit when-to-use guidance: whenever a user mentions a job by name, use list_jobs to find the matching job_id. It also provides a when-not-to-use signal by directing pipeline views to pipeline_summary instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.