Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires

hires_create_job

Create a job with taxonomy, location, salary, and workflow configuration. Primary endpoint for programmatic job publishing. Required fields: status, title, description, location_city, location_country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPublic job title.
statusYesJob status (e.g. Draft, Public). See GET /taxonomy/statuses.
form_idNoApplication form ID. If omitted, a new form named after the job title is created with default questions.
includeNoComma-separated related resources to embed: workflow, hiring_team, pipeline_stages
is_remoteNoWhether this is a remote position.
company_idNoTarget company ID. Required only when the API key has access to multiple companies.
salary_maxNoMaximum salary.
salary_minNoMinimum salary.
category_idNoJob category ID from GET /taxonomy/categories.
descriptionYesJob description (HTML allowed).
workflow_idNoWorkflow ID. If omitted, a new workflow named after the job title is created with default stages.
department_idNoDepartment ID from GET /taxonomy/departments.
location_cityYesJob city.
parent_job_idNoCanonical parent job ID. If provided, the created job becomes a satellite job.
salary_periodNoSalary period.
internal_titleNoInternal-only title visible to the hiring team.
location_stateNoJob state or region.
internal_job_idNoExternal reference ID from your ATS or HR system.
salary_currencyNoSalary currency code (e.g. USD, EUR).
location_countryYesJob country.
education_level_idNoEducation level ID from GET /taxonomy/education-levels.
employment_type_idNoEmployment type ID from GET /taxonomy/employment-types.
knockout_questionsNoBoolean knockout questions added to the application form.
ai_scoring_criteriaNoAI scoring criteria for evaluating candidates. Diff-replace by id: items with id update existing, items without id create new, existing criteria not in payload are removed. Pass [] to detach all.
experience_level_idNoExperience level ID from GET /taxonomy/experience-levels.
resume_field_statusNoResume field behavior on the application form.
location_postal_codeNoPostal or ZIP code.
location_full_addressNoFull formatted address.
location_street_addressNoStreet address.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate a write operation (readOnlyHint=false). The description adds that taxonomy lookups are used but does not disclose behavioral traits such as automatic creation of form or workflow if omitted, or idempotency. It does not contradict annotations.

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 two sentences, front-loaded with the purpose, and contains no extraneous information. Every sentence contributes value.

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?

Given 29 parameters and no output schema, the description covers required fields and general purpose but does not explain return values or what the created job object looks like. Additional detail on outcomes would improve completeness.

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 baseline is 3. The description adds grouping of parameters into categories (taxonomy, location, salary) and lists required fields, which provides some additional context beyond the schema definitions.

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 'Create', resource 'job', and scope including taxonomy, location, salary, and workflow. It distinguishes from sibling tools like hires_update_job by identifying itself as the primary endpoint for programmatic job publishing.

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 mentions it is the primary endpoint for programmatic job publishing but does not explicitly state when to use this tool versus alternatives like hires_update_job or hires_set_job_status. No guidance on prerequisites or when not to use is provided.

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 toolsInspect
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.

Resources