Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli

add_hiring_team_members

Adds sourcers, recruiters, coordinators, and hiring managers to a Greenhouse job without replacing existing team members; returns added users and per-member errors.

Instructions

Add members to a hiring team without replacing existing ones. Write operation.

To find job_id: list_jobs → match by name. For member user_ids: list_users → match by name. Returns added and any per-member errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesGreenhouse job ID
sourcersNoArray of {user_id: N} to add as sourcers
recruitersNoArray of {user_id: N, candidate_responsibility?: active|inactive|future|all} to add as recruiters
coordinatorsNoArray of {user_id: N, candidate_responsibility?: active|inactive|future|all} to add as coordinators
hiring_managersNoArray of {user_id: N} to add as hiring managers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0
  2. Removedv0.3.3
  3. Addedv0.3.4

TDQS

A4.2/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 full behavioral burden, and it does useful work: it declares 'Write operation,' clarifies the additive (non-destructive) semantics, and discloses partial-failure behavior via per-member 'errors.' It omits permission/auth requirements, which is a minor gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and its key distinction, then the ID-lookup workflow and return shape. Every sentence earns its place with no redundancy.

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?

Output schema exists, so return values need not be spelled out (though it helpfully summarizes 'added' and 'errors'). For a mutation tool with no annotations, it covers the essential write semantics and ID-sourcing prerequisites; only auth/permission context is missing.

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 all five parameters (job_id, sourcers, recruiters, coordinators, hiring_managers) are already documented, including the candidate_responsibility enum values. The description adds how to obtain IDs, but that is usage guidance rather than added meaning about the parameters themselves, 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 and resource ('Add members to a hiring team') and immediately differentiates from the sibling replace_hiring_team with 'without replacing existing ones.' An agent can distinguish this from replace_hiring_team and remove_hiring_team_member without opening any schema.

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 guidance for sourcing required IDs ('list_jobs → match by name', 'list_users → match by name') and implies when this is the right tool via the additive-not-replacing framing. It stops short of explicitly naming replace_hiring_team as the alternative to use when replacement is intended, so it is strong but not fully explicit.

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