Greenhouse Ops Control Plane

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

list_bulk_requests

List bulk operation requests in Greenhouse. Shows status, record counts, and completion details for bulk operations.

Input Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Comma-separated bulk request IDs
`active`	No	Filter by active status
`cursor`	No	Pagination cursor from a previous response. When provided, must be the only filter parameter.
`per_page`	No	Results per page (1-500, default 100)
`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
`bulk_action_uuid`	No	Filter by bulk action UUID

TDQS

A3.7/5.0

Behavior3/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. It notes that the tool lists requests and shows status, record counts, and completion details, which implies a read-only operation. However, it does not mention pagination behavior, rate limits, or any other side effects.

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, concise sentence that front-loads the purpose and key details. There is no redundant information.

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?

With no output schema, the description partially explains return values (status, record counts, completion details) but is not exhaustive. Given the tool has 7 optional parameters and complex filtering, the description could be more complete.

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?

The input schema has 100% description coverage, so all parameters are documented there. The description adds no additional meaning beyond the schema, achieving the baseline.

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 (list) and the resource (bulk operation requests), and specifies the information shown (status, record counts, completion details). This distinguishes it from sibling list tools like list_applications or list_candidates.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. It simply describes what it does, leaving usage context implicit.

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?