Greenhouse MCP

list_eeoc

Retrieve read-only EEOC compliance data—self-reported race, gender, veteran, and disability status—from applications for federal reporting.

Instructions

List all EEOC data collected from applications. Read-only.

Compliance data — self-reported race, gender, veteran, and disability status ({id, description} each). Used for federal reporting, not for hiring decisions.

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_eeoc"
  }
}

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)
`submitted_after`	No	ISO 8601 datetime — only responses submitted after this
`submitted_before`	No	ISO 8601 datetime — only responses submitted before this

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"
+}

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

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 datetime — only responses submitted after this",
+  "title": "Submitted After"
+}

addedInput schema / properties / submitted_before

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 datetime — only responses submitted before this",
+  "title": "Submitted Before"
+}

Addedv0.3.4Apr 15, 2026

TDQS

A3.7/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 full burden and does state 'Read-only', which is the safety-critical trait an agent needs. It also characterizes the payload (self-reported race, gender, veteran, disability) and flags the compliance sensitivity, though auth requirements and pagination semantics are left to the schema.

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?

Three short, front-loaded lines with the operation and read-only flag first, then payload, then usage caveat. No filler, though the parenthetical field-shape note is marginally redundant with the output schema.

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?

Output schema exists so return values needn't be re-explained, yet the description still summarizes the shape helpfully. Read-only status and the compliance context are covered; only auth/permission expectations are unstated, which is a minor gap for a read tool.

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 description coverage is 100% and all five parameters (cursor, paginate, per_page, submitted_after/before) are documented in the schema itself. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ('List all EEOC data') and scopes it to data 'collected from applications', which implicitly separates it from the sibling get_eeoc_for_application (single record). It doesn't explicitly name that sibling, so an agent must infer the aggregate-vs-single distinction.

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

Usage Guidelines3/5

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

'Used for federal reporting, not for hiring decisions' gives a usage context and a soft exclusion, but no explicit when-to-use trigger or named alternative tool. The guidance is implied rather than directive.

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

Deploy Server