Greenhouse Ops Control Plane

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

list_approval_flows

List approval flows in Greenhouse. Shows job/offer approval workflows, their status (pending/rejected/approved), and whether they are sequential.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated approval flow IDs
`cursor`	No	Pagination cursor from a previous response. When provided, must be the only filter parameter.
`job_ids`	No	Comma-separated job IDs
`per_page`	No	Results per page (1-500, default 100)
`offer_ids`	No	Comma-separated offer IDs
`created_at`	No	Filter by creation date. Format: operator\|ISO8601 (e.g. gte\|2024-01-01T00:00:00Z). Operators: gte, lte, gt, lt
`updated_at`	No	Filter by update date. Format: operator\|ISO8601 (e.g. gte\|2024-01-01T00:00:00Z). Operators: gte, lte, gt, lt
`approval_type`	No	Filter by approval type

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. However, it only describes the output content and does not mention pagination, ordering, rate limits, or other behavioral details essential for an agent.

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 sentence of 20 words, front-loaded with the resource and key output fields. Every word is useful, and there is no redundancy.

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 does not explain return format, pagination behavior, parameter interactions, or the meaning of enumerated values, leaving significant gaps.

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 schema already documents all parameters. The description adds minimal extra meaning beyond what the schema provides, meeting the baseline but not exceeding it.

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 tool lists approval flows in Greenhouse, specifying the resource (approval flows) and the information shown (status, sequentiality). It is a specific verb+resource combination that distinguishes it from other list tools.

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?

No guidance is provided on when to use this tool versus alternatives such as list_approvers or list_approver_groups. The description lacks context on prerequisites or scenarios.

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?