Greenhouse Ops Control Plane

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

remove_job_recruiter_owner

Remove a single recruiter owner from a job hiring team. Active or responsible owners require explicit override flags.

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 remove from recruiter owners
`on_behalf_of_user_id`	Yes	Greenhouse user ID to send with this write.
`allow_responsible_removal`	No	Must be true to remove a recruiter owner marked responsible.
`confirm_hiring_team_change`	Yes	Must be true to execute a hiring-team write.
`allow_active_member_removal`	No	Must be true to remove an active recruiter owner.

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only notes the need for override flags, omitting side effects, permission requirements, rate limits, or confirmation behavior. Significant gaps remain.

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?

Two concise sentences, front-loaded with the primary action. No wasted words, every phrase earns its place.

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 8 parameters, no output schema, and no annotations, the description is too brief. It lacks details on return values, the effect of dry_run, and the behavior of the confirm_hiring_team_change parameter. More context is needed for correct invocation.

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%, meeting the baseline. The description adds context about override flags mapping to parameters but does not enhance understanding of other parameters like dry_run or reason 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?

Clearly states it removes a single recruiter owner from a job hiring team, distinguishing it from adding or removing other owner types. The specific verb 'remove' and resource 'recruiter owner' make the action unambiguous.

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?

Provides a condition for using override flags (active or responsible owners) but does not explicitly state when to use this tool versus alternatives like remove_job_coordinator_owner or add_job_recruiter_owner. Guidance is implied but not comprehensive.

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?