Recruitee Ops Control Plane

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

list_admins

List admins. Company admins (recruiters and hiring managers) for resolving owner IDs to people and ranking owner workload.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`limit`	No
`cursor`	No
`include`	No
`per_page`	No
`query_json`	No	Additional documented query parameters, including bracketed filter keys.
`path_params`	No	Values for path placeholders such as {id} in a write operation.
`detail_profile`	No	operational (default) returns a compact recruiting-ops projection with names, prose, and other personal fields omitted; pass full to include the raw API payload with those fields.	operational

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJun 7, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose read-only nature, authentication needs, pagination behavior, or side effects. Only states it lists admins.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, concise but first sentence is tautological ('List admins'). Second sentence adds some context but could be more structured.

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?

Tool has 9 parameters, no output schema, and complex features (nested objects). Description lacks return value info, pagination behavior, and parameter usage details, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% with 9 parameters. Description adds no explanation for parameters like page, sort, limit, or query_json. Only 'detail_profile' has schema description; description does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'List admins' and clarifies it lists company admins (recruiters and hiring managers) with specific use cases. It distinguishes from sibling 'get_admin' but could be more precise.

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 explicit when or when-not to use. Implies use for resolving owner IDs and ranking workload, but lacks guidance on alternatives like 'get_admin' or 'list_candidates'.

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

All Recruitee 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/5.0

Disambiguation3/5

Tools are mostly distinct, but the generic api_request overlaps with all specific CRUD tools, and list_candidate_search is confusingly named and may overlap with list_candidates. Some ambiguity exists.

Naming Consistency4/5

Most tools follow a verb_noun snake_case pattern (e.g., create_candidate, get_admin), but api_request deviates as noun_noun and list_candidate_search uses a non-standard noun phrase. Overall mostly consistent.

Tool Count5/5

17 tools cover a reasonable scope for an ATS integration, including candidates, openings, admins, and supporting entities. The count feels appropriate and not overwhelming.

Completeness3/5

The surface covers core CRUD for candidates and openings, but lacks update/delete operations, notes management beyond listing, and stage management. The generic api_request tool can compensate, but the dedicated tool set has notable gaps.

Resources

Need Help?