Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_application

Change an application's source, referrer, recruiter, coordinator, or custom fields. Provide the application ID and only the fields to update.

Instructions

Update an application's source, referrer, recruiter, coordinator or custom fields. Write operation.

To find the application_id: search_candidates_by_name → get_candidate → match the application to the job. Only updates fields you provide. For source_id: list_sources. For custom field IDs: list_custom_fields. To change a rejection reason, use update_rejection_reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_idNoNew source ID — get from list_sources
referrer_idNoReferrer record ID to credit for this application
recruiter_idNoUser ID of the new recruiter — get from list_users
custom_fieldsNoArray of {custom_field_id (or name_key), value} — get field IDs from list_custom_fields
application_idYesGreenhouse application ID
coordinator_idNoUser ID of the new coordinator — get from list_users

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • addedInput schema / properties / application_id / description
      Added value: +"Greenhouse application ID"
    • addedInput schema / properties / coordinator_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "User ID of the new coordinator — get from list_users",
+  "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 / recruiter_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "User ID of the new recruiter — get from list_users",
+  "title": "Recruiter Id"
+}
    • removedInput schema / properties / referrer
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Referrer"
-}
    • addedInput schema / properties / referrer_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Referrer record ID to credit for this application",
+  "title": "Referrer Id"
+}
    • addedInput schema / properties / source_id / description
      Added value: +"New source ID — get from list_sources"
  2. Addedv0.3.4

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 behavioral burden. It does disclose that this is a write operation and that it is a partial update ('Only updates fields you provide'), which is genuinely useful. However it omits permissions/auth requirements, what happens on invalid IDs, and reversibility, leaving meaningful gaps for a mutation tool.

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 the verb, resource, and mutable fields, then layers routing hints. Every sentence is functional, though the ID-sourcing hints partly duplicate the schema and could be tightened.

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. For a six-parameter mutation tool the description covers purpose, mutable fields, ID sourcing, partial-update semantics, and a sibling alternative — nearly everything an agent needs, with only auth/permission behavior left unstated.

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 the schema already documents every parameter. The description reinforces ID sourcing (list_sources, list_custom_fields) but adds little beyond what the schema descriptions already state, so the 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 (Update) and resource (an application), and enumerates the exact mutable field categories: source, referrer, recruiter, coordinator, custom fields. It clearly differentiates from the sibling update_candidate and explicitly routes rejection-reason changes to update_rejection_reason.

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?

Provides an explicit lookup chain for application_id (search_candidates_by_name → get_candidate → match application to job), names list_sources for source_id and list_custom_fields for custom field IDs, and names the alternative tool for a distinct use case. This is when-to-use and how-to-source guidance in full.

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