open-greenhouse-mcp

list_candidates

Fetch candidate records with date-range, ID, or email filters and paginate through results for bulk operations. Read-only access to list all candidates in batches.

Instructions

List candidates with optional filters. Read-only.

For finding a specific person, use search_candidates_by_name (by name) or search_candidates_by_email (by email) — faster and simpler. Use this tool for bulk operations: date-range queries, fetching by specific IDs, or paginating through the full database.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No	Filter by exact email address
`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.
`paginate`	No	'single' for one page, 'all' to auto-fetch every page	single
`per_page`	No	Results per page (max 500)
`candidate_ids`	No	Filter to specific candidate IDs
`created_after`	No	ISO 8601 datetime — only candidates created after this
`updated_after`	No	ISO 8601 datetime — only candidates updated after this
`created_before`	No	ISO 8601 datetime — only candidates created before this
`updated_before`	No	ISO 8601 datetime — only candidates updated 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.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the safety burden, and it explicitly declares 'Read-only.' It also signals bulk-operation behavior, implying larger result sets. It doesn't cover rate limits or auth, but no side-effect ambiguity remains.

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 short sentences, front-loaded with core purpose and safety declaration. The use-case guidance is placed immediately after, and 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?

The tool has no required parameters, an output schema, and a clear role among siblings. The description supplies essential selection and safety context, while the schema handles parameter and return details, so nothing critical is missing.

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?

All 9 parameters are already documented in the input schema with 100% coverage, so the baseline applies. The description's references to date-range queries, specific IDs, and pagination map to those parameters without adding new semantic detail beyond what the schema provides.

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 'List candidates with optional filters' — a specific verb, resource, and filter concept. It then distinguishes itself from search_candidates_by_name and search_candidates_by_email, making the tool's role immediately clear.

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 states when to avoid this tool ('For finding a specific person') and names the faster, simpler alternatives. It also enumerates the intended use cases: date-range queries, fetching by specific IDs, and paginating through the full database.

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