Greenhouse Ops Control Plane

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

add_job_recruiter_owner

Add a single recruiter 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 recruiter 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 recruiter should become responsible for active candidates.
`responsible_for_future_candidates`	No	Whether this recruiter should become responsible for future candidates.
`responsible_for_inactive_candidates`	No	Whether this recruiter should become responsible for inactive candidates.

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions preview support and candidate reassignment but fails to explain that write execution requires 'confirm_hiring_team_change' to be true, the side effects on existing owners, or any authorization needs. The description is insufficient 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?

The description is a single, front-loaded sentence that efficiently communicates the core action and key features. No unnecessary words.

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

Completeness2/5

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

Given the tool has 10 parameters, 5 required, no output schema, and no annotations, the description is too sparse. It omits return behavior, error states, prerequisites, and the role of required confirmation flag. It fails to provide the needed completeness for an AI agent to use it correctly.

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 coverage is 100%, so the base is 3. The description adds context about preview support (relating to dry_run) and candidate reassignment controls (relating to responsible_for_* flags), but these are already implied in the schema descriptions. The description does not provide substantial new meaning beyond the schema.

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 verb 'Add', the specific resource 'single recruiter owner to a job hiring team', and highlights key features like preview support and candidate reassignment controls. It effectively distinguishes from sibling tools like 'add_job_coordinator_owner'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., job must exist, user must be recruiter), and no context about when to use the preview vs. write mode. The description is too brief to offer usage direction.

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?