Greenhouse MCP

list_sources

List candidate sources (job boards, referrals, agencies) to resolve a candidate's origin to a source_id for create_application or update_application. Read-only.

Instructions

List all candidate sources (job boards, referrals, agencies). Read-only.

Resolves source names to IDs for create_application and update_application. When a user mentions where a candidate came from, use this to find the source_id. Each source has a type object ({id, name}) — the sourcing strategy it rolls up to (e.g. "Referral", "Agencies").

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

Input Schema

Name	Required	Description
`cursor`	No	Pass next_cursor from the previous response to get the next page
`per_page`	No	Results per page (max 500)
`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.

Changed4 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 / per_page / description
```
Added value: +"Results per page (max 500)"
```

Addedv0.3.4Apr 15, 2026

TDQS

A4/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 behavioral burden and does state "Read-only," which is the key safety trait. It also describes the shape of the returned type object, but adds no note on pagination or cache behavior beyond what the schema already documents.

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 with the core action and the "Read-only" trait, followed by a short usage note and a data-shape note. Every sentence earns its place with no filler.

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?

An output schema exists, so return values need not be explained, and the description covers purpose, read-only status, usage, and the type object. It is broadly complete for a discovery/list tool, with only minor omissions around volume or refresh behavior that the schema already handles.

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%, so cursor, per_page, and force_refresh are fully documented in the schema. The description adds no parameter-level semantics beyond that, so the 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 specific verb and resource ("List all candidate sources") with clarifying examples (job boards, referrals, agencies) and a downstream purpose (resolving names to IDs). Clear and specific, but it does not explicitly differentiate itself from source-adjacent siblings such as source_effectiveness.

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?

Gives concrete when-to-use guidance: use it when a user mentions where a candidate came from, and it names the consumer tools (create_application, update_application) that need the source_id. No explicit when-not-use or exclusion cases are provided.

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

Deploy Server