100Hires - AI ATS & Recruitment Software

hires_submit_career_application

Submit a job application on behalf of a candidate. Creates a candidate record and triggers the career-site pipeline automation.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	Yes	Applicant email address
`phone`	No	Applicant phone number
`job_id`	Yes	Job ID to apply to
`resume`	No	Resume file upload (base64 encoded)
`source`	No	Application source identifier
`answers`	No	Array of form answer objects
`last_name`	Yes	Applicant last name
`first_name`	Yes	Applicant first name
`company_slug`	Yes	Company slug identifying the career site
`linkedin_url`	No	Applicant LinkedIn profile URL

TDQS

A3.6/5.0

Behavior4/5

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

The description adds value beyond annotations by stating the tool creates a candidate record and triggers pipeline automation. Annotations already indicate it is not read-only and not destructive, and the description aligns with that while providing specific 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 extremely concise with two short sentences, no superfluous information, and front-loads the core action. Every word contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, 5 required) and no output schema, the description provides a clear high-level purpose and side effect (triggers automation). The schema covers parameter details, so the description is sufficiently complete for an agent to understand when to use the tool.

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 baseline is 3. The description does not provide additional meaning for any specific parameters beyond what the schema already describes. It remains generic.

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?

The description clearly states the tool submits a job application and creates a candidate record, with a specific verb and resource. It also mentions triggering pipeline automation, which adds context. However, it does not explicitly distinguish from similar siblings like hires_create_application or hires_create_candidate, leaving some ambiguity.

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 hires_create_application or hires_create_candidate. There are no preconditions, when-not-to-use, or alternative suggestions.

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

All 100Hires - AI ATS & Recruitment Software 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

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.

hires_submit_career_application

Input Schema

TDQS

Glama MCP Gateway

TDQS

Resources