Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_job

Create a new Greenhouse job from a template, copying pipeline stages and settings while setting department, office, and opening details.

Instructions

Create a new job from a template. Write operation — admin only.

Users say "create a new Backend Engineer role." Requires template_job_id — use list_jobs to find a similar existing job. For department_id: list_departments → match by name. For office_ids: list_offices → match. After creation, use update_job_post to set the public listing content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoInternal notes about the job (HTML supported)
job_nameNoInternal job name
office_idsNoOffice IDs — get from list_offices
opening_idsNoOptional external IDs for the new openings, one per opening
custom_fieldsNoArray of {id, value} — get field IDs from list_custom_fields
department_idNoDepartment ID — get from list_departments
job_post_nameNoTitle for the public job post
requisition_idNoExternal requisition/req ID for HRIS mapping
template_job_idYesExisting job ID to use as template — copies pipeline stages and settings
number_of_openingsNoNumber of openings to create on this job

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.5.0
    • addedInput schema / properties / custom_fields
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Array of {id, value} — get field IDs from list_custom_fields",
+  "title": "Custom Fields"
+}
    • addedInput schema / properties / department_id / description
      Added value: +"Department ID — get from list_departments"
    • addedInput schema / properties / job_name / description
      Added value: +"Internal job name"
    • addedInput schema / properties / job_post_name / description
      Added value: +"Title for the public job post"
    • addedInput schema / properties / notes
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Internal notes about the job (HTML supported)",
+  "title": "Notes"
+}
    • addedInput schema / properties / number_of_openings / description
      Added value: +"Number of openings to create on this job"
    • addedInput schema / properties / office_ids / description
      Added value: +"Office IDs — get from list_offices"
    • addedInput schema / properties / opening_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional external IDs for the new openings, one per opening",
+  "title": "Opening Ids"
+}
    • addedInput schema / properties / requisition_id / description
      Added value: +"External requisition/req ID for HRIS mapping"
    • addedInput schema / properties / template_job_id / description
      Added value: +"Existing job ID to use as template — copies pipeline stages and settings"
  2. Addedv0.3.4

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two most important traits: it is a write operation and it is admin-only. It also fixes the required template_job_id and the post-creation workflow. It does not cover reversibility, error behavior, or how the template's pipeline/approvers propagate, which keeps it short of a 5.

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?

The write/admin declaration is front-loaded, followed by a concrete user example and then a compact ID-discovery workflow. Every sentence contributes a distinct, actionable instruction 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 no explanation, and the schema documents all 10 parameters. The description supplies behavior (write, admin-only) and the cross-tool ID-discovery workflow, making it largely complete; it could note what the template copy creates (openings, stages) but that is a minor gap.

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 genuine value beyond the schema by explaining how to derive FK values ('match by name' for department/office) and consolidating the discovery flow. It stops short of covering the remaining scalars (notes, job_name, requisition_id, number_of_openings), which the schema already documents.

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 new job') and adds the distinguishing mechanism 'from a template', which separates it from siblings like create_job_opening and update_job. An agent can identify the operation 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 prerequisites and alternatives: template_job_id via list_jobs, department_id via list_departments (match by name), office_ids via list_offices, and the follow-up step update_job_post. It also names the admin-only constraint and provides a user-phrasing example, leaving little to inference.

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

Deploy Server

Other Tools