Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

move_application

Transfer a candidate from one job to another by supplying the application ID and target job ID, with an optional starting stage.

Instructions

Transfer a candidate to a completely different job. Write operation.

Users say "move Sarah from Backend to Frontend Engineer." You need the application_id (search_candidates_by_name → get_candidate → match app) and the new_job_id (list_jobs → match by name). Optionally set a starting stage with new_stage_id (list_job_stages_for_job on the target job). The current stage is looked up automatically unless from_stage_id is given. To move within the SAME job, use move_application_same_job instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>",
      "new_job_id": "<new_job_id>"
    },
    "name": "move_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_job_idYesTarget job ID — get from list_jobs
new_stage_idNoTarget stage in new job — defaults to first stage if omitted
from_stage_idNoCurrent job_interview_stage_id (from get_application). Omit to look it up automatically
application_idYesGreenhouse application ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / application_id / description
      Added value: +"Greenhouse application ID"
    • addedInput schema / properties / from_stage_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Current job_interview_stage_id (from get_application). Omit to look it up automatically",
+  "title": "From Stage Id"
+}
    • addedInput schema / properties / new_job_id / description
      Added value: +"Target job ID — get from list_jobs"
    • addedInput schema / properties / new_stage_id / description
      Added value: +"Target stage in new job — defaults to first stage if omitted"
  2. Addedv0.3.4

TDQS

A4.5/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 meaningful behavior: it flags 'Write operation' and explains that the current stage is looked up automatically unless from_stage_id is supplied, and that new_stage_id defaults to the first stage. It stops short of stating permissions required or whether the application is detached from the original job, so it is not fully complete.

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?

Purpose is front-loaded in the first two lines and each remaining sentence (id sourcing, stage defaults, sibling routing) earns its place. Slightly plumbing-heavy in the middle but no significant waste.

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 described. The description covers purpose, required id sourcing, optional-stage behavior, and sibling disambiguation, leaving only permission/reversibility context unaddressed for an unannotated write tool.

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 already 100%, so baseline is 3, but the description adds sourcing guidance ('list_jobs', 'list_job_stages_for_job on the target job') and clarifies the auto-lookup semantics of from_stage_id, going beyond the schema text.

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 ('Transfer a candidate to a completely different job') and immediately scopes it against the same-job sibling. The agent can distinguish move_application from move_application_same_job 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?

Explicitly routes the agent: 'To move within the SAME job, use move_application_same_job instead.' It also provides the resolution workflow for required ids (search_candidates_by_name → get_candidate → match app; list_jobs → match by name) and the optional stage lookup path.

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