Greenhouse MCP

list_jobs

List jobs with optional filters to resolve job titles to job IDs, using status, department, office, or creation date filters for recruiting workflows.

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). Each job includes department and offices as {id, name}. Openings are not embedded — use list_job_openings; the hiring team is on get_job. For pipeline views, use pipeline_summary with the job_id.

Input Schema

Name	Required	Description	Default
`cursor`	No	Pass next_cursor from the previous response to get the next page
`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 at/after this
`department_id`	No	Filter to jobs in this department
`created_before`	No	ISO 8601 datetime — only jobs created before this
`requisition_id`	No	Only jobs with this exact external requisition ID

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.5.0Oct 5, 2026

addedInput schema / properties / created_after / description

Added value: +"ISO 8601 datetime — only jobs created at/after this"

addedInput schema / properties / created_before / description

Added value: +"ISO 8601 datetime — only jobs created before this"

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pass next_cursor from the previous response to get the next page",
+  "title": "Cursor"
+}

addedInput schema / properties / department_id / description
```
Added value: +"Filter to jobs in this department"
```
addedInput schema / properties / office_id / description
```
Added value: +"Filter to jobs in this office"
```

removedInput schema / properties / page

Removed value: -{
-  "default": 1,
-  "title": "Page",
-  "type": "integer"
-}

addedInput schema / properties / paginate / description

Added value: +"'single' for one page, 'all' to auto-fetch every page"

addedInput schema / properties / per_page / description
```
Added value: +"Results per page (max 500)"
```

addedInput schema / properties / requisition_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only jobs with this exact external requisition ID",
+  "title": "Requisition Id"
+}

addedInput schema / properties / status / description

Added value: +"Filter by status: 'open', 'closed', or 'draft'"

Addedv0.3.4Apr 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden — and it delivers: it declares 'Read-only' and discloses the return shape (each job includes department and offices as {id, name}; openings and hiring team are NOT embedded and where to get them). It stops short of describing pagination semantics, though the schema's cursor/paginate/per_page fields partially cover that.

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?

Front-loaded purpose and safety in the first sentence, then use case, then filters, then exclusions — every sentence carries distinct information with no redundancy.

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 9-param, no-required-filter list tool with an output schema present, the description covers purpose, triggering context, filter sourcing, embedded vs. non-embedded fields, and sibling routing. Nothing an agent needs to call it correctly 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, but the description adds cross-tool meaning: department_id is tied to list_departments and office_id to list_offices, and status values are restated with intent. This helps an agent source valid filter values rather than guess.

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+resource ('List all jobs with optional filters') and immediately differentiates itself from siblings by naming list_job_openings, get_job, and pipeline_summary with their respective roles. An agent can tell exactly what this tool does versus the other job-related 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?

Explicitly frames the primary use case (resolving job titles to job_ids), gives a concrete trigger ('When a user mentions a job by name'), and routes to alternatives with conditions: list_job_openings for openings, get_job for hiring team, pipeline_summary for pipeline views. Also points to list_departments/list_offices for the ID filters.

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

Deploy Server