Skip to main content
Glama
Greenhouse MCP

Greenhouse MCP

by benmonopoli

candidates_needing_action

Surface candidates with stale applications or missing scorecards, plus interviews awaiting feedback, sorted by urgency. Read-only.

Instructions

Find candidates that need attention — stale apps, missing scorecards. Read-only.

Users say "what needs my attention?" or "who's been sitting too long?" Pass job_id for one job (list_jobs → match by name) or omit for all active applications. Returns stale applications sorted by urgency and interviews awaiting feedback, with the interviewers whose scorecards are still missing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "candidates_needing_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoFilter to one job — list_jobs → match by name
stale_daysNoDays without activity to flag as stale

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / job_id / description
      Added value: +"Filter to one job — list_jobs → match by name"
    • addedInput schema / properties / stale_days / description
      Added value: +"Days without activity to flag as stale"
  2. Addedv0.3.4

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden and does so by declaring 'Read-only' — the single most important behavioral fact. It also previews what comes back (stale applications sorted by urgency, interviews awaiting feedback, interviewers with missing scorecards). It stops short of permissions, pagination, or result limits, which an unannotated tool arguably should mention.

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-loaded with the one-line purpose, then usage phrasings, then parameter guidance, then return shape — a sensible ordering with no filler. The only mild redundancy is repeating the 'list_jobs → match by name' mapping already present in the schema.

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 the description needn't explain return values, yet it does anyway, and it covers purpose, scoping, and both parameters. The remaining gap is the unaddressed relationship to the very similar 'stale_applications' sibling, which could cause an agent to pick the wrong 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 100%, so the baseline is 3, but the description adds real meaning the schema lacks: omitting job_id returns 'all active applications' (the schema only shows a null default), and it explains how to obtain a job_id via list_jobs. stale_days is left to the schema, which is acceptable since the schema documents it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource — 'find candidates that need attention' — and enumerates the concrete cases it covers (stale apps, missing scorecards, interviews awaiting feedback), which is far more than a restatement of the name. It does not, however, distinguish itself from the close sibling 'stale_applications' or 'pipeline_summary', leaving the agent to infer the boundary.

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?

Usage context is made explicit through the user-intent phrasings ('what needs my attention?', 'who's been sitting too long?'), which tells an agent when this tool matches a request. It also explains the two scoping modes (job_id vs omit). What's missing is any when-not-to-use guidance or an explicit pointer to the overlapping sibling tools.

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