Greenhouse Ops Control Plane

by app.vercel.ats-ops-control-plane-gateway

add_job_coordinator_owner

Add a single coordinator owner to a job hiring team, with preview support and candidate reassignment controls.

Input Schema

TableJSON Schema

Name	Required	Description
`job_id`	Yes	The Greenhouse job ID
`reason`	Yes	Human-readable audit reason for this change. Must be at least 12 characters.
`dry_run`	No	When true, validate and preview the change without sending a write request.
`user_id`	Yes	Greenhouse user ID to add as a coordinator owner
`on_behalf_of_user_id`	Yes	Greenhouse user ID to send with this write.
`confirm_hiring_team_change`	Yes	Must be true to execute a hiring-team write.
`allow_candidate_reassignment`	No	Must be true if any responsibility flag is set to true.
`responsible_for_active_candidates`	No	Whether this coordinator should become responsible for active candidates.
`responsible_for_future_candidates`	No	Whether this coordinator should become responsible for future candidates.
`responsible_for_inactive_candidates`	No	Whether this coordinator should become responsible for inactive candidates.

TDQS

A3.7/5.0

Behavior3/5

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

The description mentions preview support and candidate reassignment controls, adding some behavioral context beyond the schema, but lacks details on permissions, side effects, or error handling.

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?

The description is a single, front-loaded sentence that efficiently conveys the core purpose and key features without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (10 parameters, 5 required), the description is somewhat sparse and does not cover important aspects like the confirmation requirement, on_behalf_of_user_id, or reason field, though the schema compensates.

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?

With 100% schema description coverage, the schema already explains all parameters. The description's mention of 'preview support' and 'candidate reassignment controls' provides organizational context but does not add new semantic meaning.

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?

The description clearly states the action ('Add a single coordinator owner') and the resource ('to a job hiring team'), distinguishing it from sibling tools like add_job_recruiter_owner.

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

Usage Guidelines3/5

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

The description implies usage for adding coordinator owners but does not explicitly say when to choose this tool over alternatives or provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Greenhouse Ops Control Plane tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

With 87 tools, there is potential for confusion among similar list tools (e.g., list_candidates vs list_applied_candidate_tags), but each tool targets a distinct entity or action, and descriptions provide enough clarity to differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using lowercase with underscores (e.g., list_jobs, get_application, patch_candidate_profile). No mixing of styles or irregular conventions.

Tool Count1/5

At 87 tools, the count is extremely high for a single server, exceeding the 50+ threshold for extreme mismatch. While the domain is broad, the number of tools is likely to overwhelm agents and dilute focus.

Completeness3/5

The tool set covers a wide range of operations (list, get, patch, add, remove, upsert) across many entities, but lacks basic CRUD for core objects like jobs and candidates (no create_job or create_candidate), leaving notable gaps.

Resources

Need Help?