Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires

hires_update_job

Destructive

Update mutable job attributes. Only send fields you want to change. Preserves domain-level validation rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesJob ID (numeric) or alias
titleNoPublic job title.
statusNoJob status (e.g. Draft, Public). See GET /taxonomy/statuses.
form_idNoApplication form ID to assign to this job.
includeNoComma-separated related resources to embed: workflow, hiring_team, pipeline_stages
is_remoteNoWhether this is a remote position.
salary_maxNoMaximum salary.
salary_minNoMinimum salary.
category_idNoJob category ID from GET /taxonomy/categories.
descriptionNoJob description (HTML allowed).
workflow_idNoWorkflow ID to assign to this job.
department_idNoDepartment ID from GET /taxonomy/departments.
location_cityNoJob city.
parent_job_idNoCanonical parent job ID. If provided, the 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_countryNoJob 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. Omit to leave existing criteria untouched. 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

A4/5.0
Behavior4/5

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

The description adds value beyond annotations: it clarifies the tool performs partial updates and preserves validation rules. Annotations already indicate destructiveHint=true, but the description explains how mutations work. No contradiction found.

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: the first states the action, the second provides key usage guidance. No wasted words, and the structure is front-loaded with the verb.

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 (29 parameters, no output schema), the description is sufficient to understand its core behavior—partial updates with validation. It lacks details on side effects or omitted fields, but the schema covers parameters. Slightly above average for a mutator 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% with detailed descriptions for all 29 parameters. The description does not add extra meaning for individual parameters beyond what the schema provides, so baseline 3 is appropriate.

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 tool updates mutable job attributes, specifying the verb (update) and resource (job attributes). It distinguishes from create and get tools, and the context of siblings like hires_create_job and hires_get_job makes the purpose unambiguous.

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 provides partial guidance: 'Only send fields you want to change' instructs on partial updates, and 'Preserves domain-level validation rules' hints at behavior. However, it does not explicitly mention alternatives like hires_set_job_status for status-only changes, nor when to avoid this tool.

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