Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

move_application_same_job

Move a candidate's application directly to a chosen stage within the same job, skipping intermediate stages. Use it to advance or reroute hiring progress.

Instructions

Skip a candidate to a specific stage within the same job. Write operation.

Users say "move Sarah straight to the onsite stage" or "skip phone screen." To get the application_id: search_candidates_by_name → get_candidate → match app to job. For stage IDs: list_job_stages_for_job → find by name. The current stage is looked up automatically unless from_stage_id is given. To advance to just the next stage, use advance_application instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_stage_idYesTarget stage ID within the same job — get from list_job_stages_for_job
from_stage_idNoCandidate's current job_interview_stage_id. Omit to look it up automatically
application_idYesGreenhouse application ID

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 / from_stage_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / from_stage_id / default
      Added value: +null
    • addedInput schema / properties / from_stage_id / description
      Added value: +"Candidate's current job_interview_stage_id. Omit to look it up automatically"
    • removedInput schema / properties / from_stage_id / type
      Removed value: -"integer"
    • addedInput schema / properties / to_stage_id / description
      Added value: +"Target stage ID within the same job — get from list_job_stages_for_job"
    • changedInput schema / required
      Previous value: -[
-  "application_id",
-  "from_stage_id",
-  "to_stage_id"
-]New value: +[
+  "application_id",
+  "to_stage_id"
+]
  2. Addedv0.3.4

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 burden; it does declare 'Write operation' and discloses the non-obvious behavior that the current stage is auto-looked-up unless from_stage_id is given. It does not mention side effects such as notifications, stage-history entries, or permission requirements, leaving some behavioral 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-loaded with the core action and write nature, then the user-phrasing examples and lookup workflow. Every line is useful, though the quoted user phrasings overlap slightly with the opening sentence and could be trimmed.

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 values need no explanation. Between the purpose, the alternative-tool routing, and the ID-resolution workflow, an agent has everything needed to invoke this three-parameter mutation correctly.

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 baseline is 3, but the description adds genuine value by explaining how to obtain each ID (application_id via search_candidates_by_name → get_candidate, stage IDs via list_job_stages_for_job) and why from_stage_id is optional. This goes beyond the schema's terse field 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?

Specific verb ('skip/move') plus a precise resource ('a candidate to a specific stage within the same job'), and it is explicitly distinguished from move_application (cross-job) and advance_application (next stage only). An agent can pick it 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?

States exactly when to use it ('skip phone screen', 'move straight to onsite') and when not to ('to advance to just the next stage, use advance_application instead'), naming the alternative tool. It also gives the prerequisite lookup chains for application_id and stage IDs.

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