Greenhouse MCP

add_prospect

Create a sourced prospect in a prospect pool, not tied to an active job pipeline. Add names, contact info, pool and stage IDs for later conversion to candidates.

Instructions

Create a sourced prospect in a prospect pool. Write operation.

Users say "add this person as a prospect for the Engineering pool." Unlike create_candidate with a job_id, this creates a prospect not yet in an active job pipeline. For pool/stage IDs: list_prospect_pools → match by name. To later convert to an active candidate, use convert_prospect.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Current job title
`company`	No	Current company name
`job_ids`	No	Jobs this prospect is being considered for — from list_jobs
`last_name`	Yes	Prospect's last name
`first_name`	Yes	Prospect's first name
`phone_numbers`	No	Array of {value: '+1...', type: 'mobile'\|'home'\|'work'}
`email_addresses`	No	Array of {value: 'x@y.com', type: 'personal'\|'work'}
`prospect_pool_id`	No	Prospect pool to add to — get from list_prospect_pools
`prospect_owner_id`	No	User ID who owns this prospect — get from list_users
`prospect_stage_id`	No	Stage within the prospect pool

Output Schema

TableJSON 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 / company / description
```
Added value: +"Current company name"
```

addedInput schema / properties / email_addresses / description

Added value: +"Array of {value: 'x@y.com', type: 'personal'|'work'}"

addedInput schema / properties / first_name / description
```
Added value: +"Prospect's first name"
```

addedInput schema / properties / job_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Jobs this prospect is being considered for — from list_jobs",
+  "title": "Job Ids"
+}

addedInput schema / properties / last_name / description
```
Added value: +"Prospect's last name"
```

addedInput schema / properties / phone_numbers / description

Added value: +"Array of {value: '+1...', type: 'mobile'|'home'|'work'}"

addedInput schema / properties / prospect_owner_id / description

Added value: +"User ID who owns this prospect — get from list_users"

addedInput schema / properties / prospect_pool_id / description

Added value: +"Prospect pool to add to — get from list_prospect_pools"

addedInput schema / properties / prospect_stage_id / description
```
Added value: +"Stage within the prospect pool"
```
addedInput schema / properties / title / description
```
Added value: +"Current job title"
```

Addedv0.3.4Apr 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key trait 'Write operation' and clarifies the object is a prospect not yet in an active pipeline. However it omits permission requirements, behavior on duplicate prospects, and any error/validation semantics that a mutation tool should surface.

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?

Content is front-loaded with the operation and mutation flag, and each subsequent sentence adds routing value. Slightly verbose with a redundant restatement of the ID-sourcing already in the schema, but no dead weight.

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. Combined with 100% schema coverage, the description supplies the routing, mutation flag, and ID resolution an agent needs. Missing only edge-case behavior (duplicates, permissions) for full completeness.

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 each of the 10 parameters is already documented in the schema (including the list_prospect_pools / list_users sourcing hints). The description's 'For pool/stage IDs: list_prospect_pools → match by name' largely restates that, adding little new meaning. Baseline 3 applies.

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 and resource ('Create a sourced prospect in a prospect pool') and explicitly distinguishes itself from create_candidate (job_id → pipeline) and convert_prospect. An agent can select this correctly without opening the schema.

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?

Gives explicit when-to-use ('Users say add this person as a prospect for the pool'), when-not (unlike create_candidate with job_id), the ID-resolution path (list_prospect_pools → match by name), and the follow-up tool (convert_prospect). Routing is fully specified.

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

Deploy Server