Greenhouse MCP

create_candidate

Add a new candidate record to Greenhouse and optionally apply them to a job in one call. Check for duplicates first, then create the candidate and application together.

Instructions

Create a new candidate record, optionally applying them to a job. Write operation.

Users say "add a new candidate — Jane Doe at Acme Corp for the Backend role." Check for duplicates first with search_candidates_by_name or search_candidates_by_email. Pass job_id (list_jobs) to create the application in the same call; the response then has both candidate and application. Without job_id, use create_application afterwards. For sourced prospects, use add_prospect instead.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No	Candidate tag names to apply
`title`	No	Current job title
`job_id`	No	Also apply them to this job (list_jobs) in the same call
`company`	No	Current company name
`addresses`	No	Array of {value: '123 Main St', type: 'home'\|'work'\|'other'}
`last_name`	Yes	Candidate's last name
`source_id`	No	Application source ID (list_sources) — needs job_id
`first_name`	Yes	Candidate's first name
`referrer_id`	No	Referrer record ID — needs job_id
`recruiter_id`	No	Recruiter user ID (list_users) — needs job_id
`custom_fields`	No	Array of {custom_field_id (or name_key), value} — get field IDs from list_custom_fields
`phone_numbers`	No	Array of {value: '+1...', type: 'mobile'\|'home'\|'work'\|'other'}
`coordinator_id`	No	Coordinator user ID (list_users) — needs job_id
`email_addresses`	No	Array of {value: 'x@y.com', type: 'personal'\|'work'\|'other'}
`initial_stage_id`	No	Starting interview stage (list_job_stages_for_job) — needs job_id

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.5.0Oct 5, 2026

addedInput schema / properties / addresses / description

Added value: +"Array of {value: '123 Main St', type: 'home'|'work'|'other'}"

addedInput schema / properties / company / description
```
Added value: +"Current company name"
```

addedInput schema / properties / coordinator_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Coordinator user ID (list_users) — needs job_id",
+  "title": "Coordinator Id"
+}

addedInput schema / properties / custom_fields / description

Added value: +"Array of {custom_field_id (or name_key), value} — get field IDs from list_custom_fields"

addedInput schema / properties / email_addresses / description

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

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

addedInput schema / properties / initial_stage_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Starting interview stage (list_job_stages_for_job) — needs job_id",
+  "title": "Initial Stage Id"
+}

addedInput schema / properties / job_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Also apply them to this job (list_jobs) in the same call",
+  "title": "Job Id"
+}

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

addedInput schema / properties / phone_numbers / description

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

addedInput schema / properties / recruiter_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Recruiter user ID (list_users) — needs job_id",
+  "title": "Recruiter Id"
+}

addedInput schema / properties / referrer_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Referrer record ID — needs job_id",
+  "title": "Referrer Id"
+}

addedInput schema / properties / source_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Application source ID (list_sources) — needs job_id",
+  "title": "Source Id"
+}

addedInput schema / properties / tags / description
```
Added value: +"Candidate tag names to apply"
```
addedInput schema / properties / title / description
```
Added value: +"Current job title"
```

Addedv0.3.4Apr 15, 2026

TDQS

A4.6/5.0

Behavior4/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, and it does disclose the mutation nature ('Write operation'), the response shape when job_id is passed, and the duplicate-check prerequisite. It stops short of covering permissions/authorization requirements or what happens if a duplicate is detected (hard error vs. soft match).

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-loads purpose and write-type in the first line, then adds usage flow. The embedded user quote is slightly verbose but earns its place by illustrating the job_id-in-the-same-call pattern; otherwise tight.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers the create/apply fork, the duplicate-check step, and the sibling alternative. For a 15-param create tool with full schema coverage, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining the job_id side effect (application created in the same call, response contains both) and the fallback to create_application when it is omitted. Other params are left to the rich schema descriptions.

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?

Opens with a specific verb+resource ('Create a new candidate record') and states scope ('optionally applying them to a job'). It explicitly differentiates from siblings, naming add_prospect and create_application, so an agent can route correctly without opening a 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 rules: check duplicates first with search_candidates_by_name or search_candidates_by_email; pass job_id to fold the application into the same call; without job_id use create_application afterwards. It also names the alternative tool (add_prospect) with the condition (sourced prospects) that selects it.

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

Deploy Server