Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

bulk_advance

Move multiple job applications to their next interview stage at once, optionally limiting moves to applications currently in a specified stage. Rejected, hired, and prospect applications are skipped.

Instructions

Advance multiple applications to the next stage. Write operation — rate-limited.

Users say "move everyone past phone screen forward." Get application_ids from pipeline_summary or list_applications. Each application moves from its current stage to the next one on its job's interview plan. Optionally pass from_stage_id (list_job_stages_for_job → match by name) to only advance applications currently in that stage — others are skipped. Rejected, hired or prospect applications are skipped. Processes sequentially with rate-limit delays.

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_ids": "<application_ids>"
    },
    "name": "bulk_advance"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_stage_idNoOnly advance apps currently in this job interview stage (list_job_stages_for_job → match by name); omit to advance each from its current stage
application_idsYesApplication IDs to advance

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / application_ids / description
      Added value: +"Application IDs to advance"
    • addedInput schema / properties / from_stage_id / description
      Added value: +"Only advance apps currently in this job interview stage (list_job_stages_for_job → match by name); omit to advance each from its current stage"
  2. Addedv0.3.3

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it declares this is a write operation, that it is rate-limited, that processing is sequential with rate-limit delays, and enumerates the skip rules (rejected/hired/prospect apps, and apps not currently in from_stage_id).

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?

Front-loads the operation and its write/rate-limit nature, then adds usage, mechanics, and edge cases in compact sentences with no filler. Every sentence conveys a distinct fact an agent needs.

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?

Both parameters are documented, an output schema exists so return values need no explanation, and the description covers the mutation semantics, rate limiting, and skip behavior for a bulk write tool with no annotations.

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 goes further by explaining the skip consequence of from_stage_id ('others are skipped'), how to derive it (list_job_stages_for_job, match by name), and where to obtain application_ids, which the schema does not say.

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 (advance), resource (applications), and scope (multiple / bulk) in the first clause, which cleanly separates it from the single-application sibling advance_application. It also names the exact state transition: each app moves to the next stage on its job's interview plan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing for inputs ('Get application_ids from pipeline_summary or list_applications'), a real user phrasing that triggers it, and a clear condition for when to use from_stage_id. It never explicitly says to use advance_application for a single app, but the bulk framing and the source-tool pointers cover the practical decision.

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