hires_list_statuses
Read-only
List job status labels (draft, published, on_hold, closed, archived). Cache to validate job status updates.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
100Hires - AI ATS & Recruitment Software
by com.100hires
TDQS
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by enumerating the statuses returned (draft, published, on_hold, closed, archived) and suggesting caching, which aids intelligent invocation.
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 with no wasted words. The verb and resource are front-loaded, and every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless tool with no output schema, the description provides the resource, examples, and a usage hint. It is fully adequate for an agent to select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters with 100% coverage, so no parameter documentation is needed. The description compensates by listing expected output values, which is ideal.
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 'list' and the resource 'job status labels', and provides specific examples (draft, published, on_hold, closed, archived). It is distinct from sibling tools like 'hires_list_jobs' or 'hires_list_workflow_stages'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description hints at usage for validation ('Cache to validate job status updates'), but does not explicitly state when to use or avoid this tool, nor compare it to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have clearly distinct purposes due to specific entity and action combinations. However, with 133 tools, there is some overlap (e.g., multiple ways to move applications) and similar-sounding operations (e.g., batch_remove_tags vs remove_candidate_tag) that could cause confusion. The detailed descriptions help but the sheer number increases ambiguity.
Naming Consistency5/5
All tools follow a consistent 'hires_verb_noun' pattern with snake_case. Verbs are descriptive (create, list, get, delete, update, batch) and nouns match the domain entities (candidate, application, job, etc.). No mixing of conventions like camelCase or inconsistent verb styles.
Tool Count2/5
133 tools is excessive for a typical server scope. While a full-featured ATS requires many operations, this count suggests insufficient aggregation. Tools for similar entities (e.g., multiple update/delete variants) could be consolidated. The high number overwhelms the tool surface and increases complexity.
Completeness4/5
The tool set covers core CRUD operations for major entities (candidates, applications, jobs, companies, users, messages, forms, etc.) plus batch operations, webhooks, and advanced features like AI scoring and nurture campaigns. Minor gaps exist (e.g., no direct reporting/analytics tools), but most workflows can be executed.