Greenhouse MCP

list_departments

Retrieve all departments read-only to resolve names to IDs for job listings, job creation, or permissions, and rebuild the hierarchy using parent_id.

Instructions

List all departments. Read-only.

Resolves department names to IDs. When a user mentions a department ("Engineering"), use this to find its ID for list_jobs, create_job, or add_future_job_permission. Each department has parent_id (null for top level); rebuild the tree from parent_id.

Input Schema

Name	Required	Description	Default
`cursor`	No	Pass next_cursor from the previous response to get the next page
`paginate`	No	'single' for one page, 'all' to auto-fetch every page	single
`per_page`	No	Results per page (max 500)
`parent_id`	No	Only departments directly under this parent department
`force_refresh`	No	Bypass cache and fetch fresh data

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.0Oct 5, 2026

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 / force_refresh / description
```
Added value: +"Bypass cache and fetch fresh data"
```

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 / parent_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only departments directly under this parent department",
+  "title": "Parent Id"
+}

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

Addedv0.3.4Apr 15, 2026

TDQS

A4.1/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 behavioral burden. It declares read-only safety and adds a real output-shape fact not in the schema: each department has parent_id (null = top level) and the tree must be rebuilt from it. Cache/pagination behavior is only in the schema, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose, then 'Read-only', then progressively optional detail. All three sentences earn a place. The phrasing is slightly terser than ideal but not padded.

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 list/read tool with an output schema and full parameter coverage, this is nearly complete. The only gaps are explicit when-not-to-use guidance and cache/pagination context, both minor given schema coverage.

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 coverage is 100%, so cursor, paginate, per_page, parent_id, and force_refresh are already fully documented. The description adds no parameter-level detail beyond what the schema provides, so it sits at the baseline.

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 departments') and immediately clarifies the real-world purpose and downstream consumers (list_jobs, create_job, add_future_job_permission), which clearly distinguishes it from siblings like get_department, create_department, and list_board_departments.

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

Usage Guidelines4/5

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

Explicitly tells the agent when to reach for it: when a user mentions a department by name and its ID is needed. That is a strong use-case trigger. It doesn't mention when NOT to use it (e.g., single known ID vs get_department), so it falls just short of 5.

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

Deploy Server