Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

100Hires - AI ATS & Recruitment Software

REMOTE · MCP.100HIRES.COM · SCANNED AUG 3

Official 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.

Available components

+8 this week 84 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 13972 tokens (~99/item across 141 items; 133 tools + 8 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.100hires.com

# add to Claude Code
claude mcp add --transport http com-100hires-100hires https://mcp.100hires.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-100hires-100hires]
url = "https://mcp.100hires.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-100hires-100hires": {
      "type": "remote",
      "url": "https://mcp.100hires.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-100hires-100hires --url https://mcp.100hires.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-100hires-100hires:
    url: "https://mcp.100hires.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-100hires-100hires": {
      "type": "http",
      "url": "https://mcp.100hires.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +5
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 76

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.100hires.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=100hires.com CN=WE1,O=Google Trust Services,C=US 6 Jun 2026 4 Sept 2026 ECDSA 256 ECDSA-SHA256 187d26916609fccc0efa54133a9855b2
SANs: 100hires.com, *.100hires.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.100hires.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
100hires.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.100hires.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid Authorization header"

Bearer resource_metadata="https://mcp.100hires.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="Missing or invalid Authorization header"
Header Value
strict-transport-security max-age=31536000
content-security-policy img-src https: data:; upgrade-insecure-requests

Protected resource metadata

Document https://mcp.100hires.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.100hires.com/mcp
Authorisation server https://mcp.100hires.com
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.100hires.com/mcp Verified 200
http (plaintext) http://mcp.100hires.com/mcp HTTPS enforced 301 https://mcp.100hires.com/mcp
MCP tools — 133 exposed · ~13,864 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
hires_add_candidate_tags ~62

Add one or more tags to a candidate. Used for campaign tagging, qualification labels, and source attribution.

NameTypeReqDescription
idstring|numberyesCandidate ID (integer) or alias (string).
tagsarrayyesArray of tag strings to add.

No output schema declared.

No examples provided.

hires_add_hiring_team_member ~63

Add a company member to the job's hiring team. Use in workflow setup and ownership automation.

NameTypeReqDescription
idstring|numberyesJob ID (numeric) or alias
user_idnumberyesUser ID to add to the hiring team.

No output schema declared.

No examples provided.

hires_advance_application ~132

Advance an application to the next pipeline stage according to workflow order. No stage_id needed -- the system determines the next stage automatically. **Always pass `include=candidate,job`** when surfacing results in the widget — without it, the confirmation card can only show candidate/job IDs and cannot link to their backoffice pages.

NameTypeReqDescription
idnumberyesApplication ID.
includestringComma-separated relations to embed: candidate, cv.text, job. Set to `candidate,job` so the widget can link the candidate name to their profile and the job title to its pipeline view.

No output schema declared.

No examples provided.

hires_batch_add_tags ~58

Add tags to multiple candidates in one request (max 100). Returns per-item results with partial success support.

NameTypeReqDescription
idsarrayyesCandidate IDs to tag (max 100).
tagsarrayyesTag names to attach.

No output schema declared.

No examples provided.

hires_batch_create_messages ~73

Create up to 100 scheduled messages in one request. Each item specifies its own candidate_id and message payload. Items are processed independently -- one failure does not stop others. Per-candidate RBAC is enforced for each item.

NameTypeReqDescription
messagesarrayyesArray of message payloads to create (max 100).

No output schema declared.

No examples provided.

hires_batch_job_boards ~43

Get board publication states for multiple jobs in one request. Optimized for batch monitoring and management UIs.

NameTypeReqDescription
jobsarrayyesArray of job IDs

No output schema declared.

No examples provided.

hires_batch_move_applications ~66

Move multiple applications to a pipeline stage in one request. Returns per-item results with partial success support. Max 100 application IDs per request.

NameTypeReqDescription
idsarrayyesApplication IDs to move (max 100).
stage_idnumberyesTarget pipeline stage ID.

No output schema declared.

No examples provided.

hires_batch_publish_to_boards ~65

Activate board publication for multiple jobs in one request. Use for bulk job distribution workflows.

NameTypeReqDescription
boardsarrayArray of board identifiers to activate (e.g. ['indeed', 'linkedin'])
jobsarrayyesArray of job IDs to publish

No output schema declared.

No examples provided.

hires_batch_reject_applications ~69

Reject multiple applications in one request with an optional rejection reason. Returns per-item results with partial success support. Max 100 application IDs per request.

NameTypeReqDescription
idsarrayyesApplication IDs to reject (max 100).
rejection_reason_idnumberOptional rejection reason ID.

No output schema declared.

No examples provided.

hires_batch_remove_from_boards ~67

Deactivate board publication for multiple jobs in one request. Use for bulk depublishing workflows.

NameTypeReqDescription
boardsarrayArray of board identifiers to deactivate (e.g. ['indeed', 'linkedin'])
jobsarrayyesArray of job IDs to depublish

No output schema declared.

No examples provided.

hires_batch_remove_tags ~60

Remove tags from multiple candidates in one request (max 100). Returns per-item results with partial success support.

NameTypeReqDescription
idsarrayyesCandidate IDs to remove tags from (max 100).
tagsarrayyesTag names to remove.

No output schema declared.

No examples provided.

hires_cancel_all_notification_messages ~49

Cancel all scheduled notification emails for a candidate. Already sent notifications are not affected. Returns success even if no scheduled notifications exist.

NameTypeReqDescription
candidate_idyesCandidate ID (numeric) or alias.

No output schema declared.

No examples provided.

hires_create_application ~121

Create an application by linking an existing candidate to a job. Use for sourcing workflows and manual application ingestion. The candidate must already exist.

NameTypeReqDescription
candidate_idstring|numberyesCandidate ID (numeric) or alias.
cvobjectOptional CV/resume to attach.
includestringComma-separated relations to embed: candidate, cv.text, job.
job_idnumberyesJob ID to apply the candidate to.
stage_idnumberPipeline stage ID. If omitted, defaults to the first stage.

No output schema declared.

No examples provided.

hires_create_candidate ~367

Create a new candidate profile. Optionally link to a job/stage and attach the candidate's resume as extracted text. Used for imports, inbound forms, and enrichment workflows. When the user provides an attached resume (PDF/DOCX/etc.), parse the file content yourself from the chat context — LLMs natively extract text from uploaded files — and pass the extracted text via resume_text. Do NOT attempt to inline binary file data: host function-call serializers truncate arguments above ~20KB.

NameTypeReqDescription
citystringCandidate city for location/timezone resolution.
company_idnumberTarget company ID. Required only when the API key has access to multiple companies.
countrystringCandidate country name or ISO code.
emailstringCandidate email address. Used for deduplication.
first_namestringCandidate first name.
job_idnumberJob ID to create an application for this candidate.
last_namestringCandidate last name.
phonestringCandidate phone number.
profileobjectKey-value map of profile field answers. Keys can be question text or question_id. Example: {"Current job title": "Senior Engineer"}.
resume_textstringPlain-text resume content extracted by the model from an attached PDF/DOCX/etc. Stored as a text/plain attachment on the candidate. Do not pass binary or base64 here — only the parsed text content.
stage_idnumberPipeline stage ID for the initial application. Requires job_id.
statestringCandidate state or region.
timezonestringIANA timezone (e.g. 'America/Los_Angeles'). Auto-resolved from city/country if omitted.

No output schema declared.

No examples provided.

hires_create_company ~140

Create a client company (partner tenant) — provisions its public career-site URL (slug) and public branding (logo, name). Typical entrypoint for multi-tenant onboarding.

NameTypeReqDescription
company_owner_emailstringyesCompany owner email address
company_owner_namestringyesCompany owner full name
company_owner_phonestringCompany owner phone number
is_staffing_agencybooleanWhether this company is a staffing agency
logoobjectCompany logo file
namestringyesCompany name
urlstringCompany profile URL
websitestringCompany website URL

No output schema declared.

No examples provided.

hires_create_email_template ~134

Create a new email template with name, subject, and body. Subject and body support placeholders like {{first_name}}, {{job_title}}. To embed placeholders: 1) GET /template-placeholders to list them, 2) POST /template-placeholders/prepare to get the HTML tag, 3) insert the tag into the body.

NameTypeReqDescription
bodystringyesEmail body HTML (supports placeholders)
company_idnumberTarget company ID
namestringyesTemplate name
subjectstringyesEmail subject line (supports placeholders like {{first_name}}, {{job_title}})

No output schema declared.

No examples provided.

hires_create_form ~58

Create a new application form, optionally attaching existing questions by ID.

NameTypeReqDescription
company_idnumberTarget company ID.
namestringyesForm name.
questionsarrayArray of question IDs to attach to this form.

No output schema declared.

No examples provided.

hires_create_interview ~144

Schedule a new interview for an application. Provide start/end times as Unix timestamps and a list of interviewer user IDs. Location is resolved to an existing record or created automatically.

NameTypeReqDescription
end_timenumberyesInterview end time as Unix timestamp (seconds, must be after start_time).
idnumberyesApplication ID.
includestringComma-separated relations to embed: candidate, application, job.
interviewer_idsarrayyesList of user IDs who will conduct the interview.
locationstringLocation string; resolved to existing record or created automatically.
start_timenumberyesInterview start time as Unix timestamp (seconds).

No output schema declared.

No examples provided.

hires_create_job ~556

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.

NameTypeReqDescription
ai_scoring_criteriaarrayAI 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.
category_idnumberJob category ID from GET /taxonomy/categories.
company_idnumberTarget company ID. Required only when the API key has access to multiple companies.
department_idnumberDepartment ID from GET /taxonomy/departments.
descriptionstringyesJob description (HTML allowed).
education_level_idnumberEducation level ID from GET /taxonomy/education-levels.
employment_type_idnumberEmployment type ID from GET /taxonomy/employment-types.
experience_level_idnumberExperience level ID from GET /taxonomy/experience-levels.
form_idnumberApplication form ID. If omitted, a new form named after the job title is created with default questions.
includestringComma-separated related resources to embed: workflow, hiring_team, pipeline_stages
internal_job_idstringExternal reference ID from your ATS or HR system.
internal_titlestringInternal-only title visible to the hiring team.
is_remotebooleanWhether this is a remote position.
knockout_questionsarrayBoolean knockout questions added to the application form.
location_citystringyesJob city.
location_countrystringyesJob country.
location_full_addressstringFull formatted address.
location_postal_codestringPostal or ZIP code.
location_statestringJob state or region.
location_street_addressstringStreet address.
parent_job_idnumberCanonical parent job ID. If provided, the created job becomes a satellite job.
resume_field_statusstringResume field behavior on the application form.
salary_currencystringSalary currency code (e.g. USD, EUR).
salary_maxnumberMaximum salary.
salary_minnumberMinimum salary.
salary_periodstringSalary period.
statusstringyesJob status (e.g. Draft, Public). See GET /taxonomy/statuses.
titlestringyesPublic job title.
workflow_idnumberWorkflow ID. If omitted, a new workflow named after the job title is created with default stages.

No output schema declared.

No examples provided.

hires_create_job_webhook ~102

Register a webhook URL for job-related events. Core step for outbound integration setup. URL must be HTTPS. Returns a signing_secret once — store it to verify the x-hires-signature-v2 header on incoming deliveries.

NameTypeReqDescription
idstring|numberyesJob ID (numeric) or alias
urlstringyesWebhook destination URL. Must be HTTPS and point to a public host (no localhost / private / link-local IPs).

No output schema declared.

No examples provided.

hires_create_note ~210

Create a discussion note for a candidate. Supports visibility control (all or private) and @mentions with email notifications. **Always pass `include=candidate`** when surfacing results in the widget — without it, the confirmation card can only show the candidate ID and cannot link to their backoffice profile.

NameTypeReqDescription
bodystringyesNote content. Supports HTML.
candidate_idstring|numberyesCandidate ID (numeric) or alias
includestringInclude related resources, e.g. 'user' for author details, 'candidate' for full candidate object with url_backoffice. Set to `candidate` so the widget can link the candidate name to their backoffice…
mention_user_idsarrayArray of user IDs to mention. Mentioned users receive email notifications.
user_idnumberAuthor user ID. If omitted, the authenticated user is used
visibilitystringVisibility: 'all' (default) or 'private'

No output schema declared.

No examples provided.

hires_create_nurture_campaign ~232

Create a nurture campaign with steps. Steps are executed sequentially; each step has a type (email, sms, voicemail, move_to_next_stage, assign_tag, assign_task) with type-specific fields. Optionally bind to a workflow stage.

NameTypeReqDescription
company_idnumberTarget company ID (optional if API key is scoped to one company)
delay_timenumberDelay time in seconds
relative_daysnumberRelative days for schedule
relative_timenumberRelative time for schedule (seconds from midnight)
response_move_to_stage_idnumberStage to move candidate to when they reply
send_to_allbooleanSend to all candidates or only new ones (default false)
stage_idnumberStage ID that triggers the campaign
stepsarrayyesCampaign steps (at least one required)
timezonestringIANA timezone, e.g. "America/New_York"
titlestringyesCampaign name
workflow_idnumberWorkflow ID to bind the campaign to

No output schema declared.

No examples provided.

hires_create_question ~85

Create a reusable question with optional answer options for dropdown types. Used by forms and questionnaires.

NameTypeReqDescription
company_idnumberTarget company ID (uses default company when omitted)
optionsarrayAnswer options (for select/multiselect question types)
textstringyesQuestion text
typestringyesQuestion type (from hires_list_question_types)

No output schema declared.

No examples provided.

hires_create_webhook ~89

Create a company-scoped webhook subscription. Use for outbound company-level event integrations. Returns a signing_secret once — store it to verify the x-hires-signature-v2 header on incoming deliveries.

NameTypeReqDescription
idnumberyesCompany ID
urlstringyesWebhook destination URL. Must be HTTPS and point to a public host (no localhost / private / link-local IPs).

No output schema declared.

No examples provided.

hires_delete_application ~34

Permanently delete an application. This removes it from all list and view queries.

NameTypeReqDescription
idnumberyesApplication ID.

No output schema declared.

No examples provided.

hires_delete_candidate ~37

Permanently delete a candidate by ID or alias.

NameTypeReqDescription
idstring|numberyesCandidate ID (integer) or alias (string).

No output schema declared.

No examples provided.

hires_delete_company ~42

Delete (soft-delete) a company — takes its public career site offline. Use for lifecycle control in partner tenancy management.

NameTypeReqDescription
idnumberyesCompany ID

No output schema declared.

No examples provided.

hires_delete_email_template ~40

Soft-delete an email template. Templates already used in automations will stop being available for new actions.

NameTypeReqDescription
idnumberyesEmail template ID

No output schema declared.

No examples provided.

hires_delete_form ~23

Delete an application form.

NameTypeReqDescription
idnumberyesForm ID.

No output schema declared.

No examples provided.

hires_delete_job ~40

Delete a job. Use to align archived/removed positions across integrated platforms.

NameTypeReqDescription
idstring|numberyesJob ID (numeric) or alias

No output schema declared.

No examples provided.

hires_delete_job_webhook ~58

Delete a job webhook subscription by ID. Use for cleanup, rotation, and endpoint migration.

NameTypeReqDescription
idstring|numberyesJob ID (numeric) or alias
webhook_idnumberyesWebhook ID to delete

No output schema declared.

No examples provided.

hires_delete_message ~31

Cancel a scheduled message before it is processed by the mailbox scheduler.

NameTypeReqDescription
idintegeryesMessage ID.

No output schema declared.

No examples provided.

hires_delete_note ~31

Delete a note. Use for moderation policies and data cleanup operations.

NameTypeReqDescription
idnumberyesNote ID

No output schema declared.

No examples provided.

hires_delete_notification_message ~38

Cancel a scheduled notification email before it is sent. Already sent messages cannot be canceled.

NameTypeReqDescription
idintegeryesNotification email message ID.

No output schema declared.

No examples provided.

hires_delete_nurture_campaign ~40

Delete (soft-delete) a nurture campaign. Active campaign executions will be stopped.

NameTypeReqDescription
idnumberyesNurture campaign ID

No output schema declared.

No examples provided.

hires_delete_question ~35

Delete a reusable question from the catalog. Use cautiously when deprecating question banks.

NameTypeReqDescription
idnumberyesQuestion ID

No output schema declared.

No examples provided.

hires_delete_webhook ~48

Delete a company-scoped webhook subscription by ID. Use for endpoint retirement and security rotation.

NameTypeReqDescription
idnumberyesCompany ID
webhook_idnumberyesWebhook ID

No output schema declared.

No examples provided.

hires_disqualify_candidate ~71

Disqualify a candidate from all active applications. Optionally provide rejection reason IDs. Returns affected application IDs.

NameTypeReqDescription
idstring|numberyesCandidate ID (integer) or alias (string).
reasonsarrayArray of rejection reason IDs from GET /taxonomy/rejection-reasons.

No output schema declared.

No examples provided.

hires_download_attachment ~171

Download an attachment (resume, candidate file, application file, mail attachment, call recording). Pass the absolute URL returned by another endpoint (e.g. `message.attachments[].url`, `cv.url`, `resume.url`) — it MUST belong to the configured 100Hires API host; other hosts are rejected to avoid leaking the Bearer token. Returns `{file_name, mime_type, size, data}` where `data` is base64-encoded bytes. Files larger than 25 MB are rejected up-front (Content-Length check / streaming abort) without being loaded into memory.

NameTypeReqDescription
urlstringyesAbsolute attachment URL returned by another API response (e.g. https://api.100hires.com/v2/attachments/mail_attachment/<uuid>/<file_name>). Must match the API host.

No output schema declared.

No examples provided.

hires_get_ai_score ~55

Get the structured AI score for an application, including per-criterion scores, justifications, and follow-up questions. Returns null score if the application has not been AI-scored.

NameTypeReqDescription
idnumberyesApplication ID.

No output schema declared.

No examples provided.

hires_get_application ~58

Get full application details including stage, status, and rejection context. Recommended before mutating stage transitions.

NameTypeReqDescription
idnumberyesApplication ID.
includestringComma-separated relations to embed: candidate, cv.text, job.

No output schema declared.

No examples provided.

hires_get_billing ~29

Get billing/pricing capability flags for the current company. Use before invoking paid-only API behaviors.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

hires_get_candidate ~40

Get full candidate data including application summaries by candidate ID or alias.

NameTypeReqDescription
idstring|numberyesCandidate ID (integer) or alias (string).

No output schema declared.

No examples provided.

hires_get_candidate_resume ~112

Get the primary resume for a candidate. Returns uuid, absolute download url (use Bearer auth), relative_time, file metadata, type. Use include='text_content' to also get the parsed plain-text content in a `text` field without downloading the file.

NameTypeReqDescription
idstring|numberyesCandidate ID (integer) or alias (string).
includestringComma-separated optional fields. Use 'text_content' to add a `text` field with parsed plain-text resume content.

No output schema declared.

No examples provided.

hires_get_career_job ~71

Get full details of a single public job by ID. Returns salary, education level, experience level, and other extended fields. Returns 404 for draft, archived, or internal jobs.

NameTypeReqDescription
company_slugstringyesCompany slug identifying the career site
idnumberyesJob ID

No output schema declared.

No examples provided.

hires_get_company ~33

Get company profile and owner metadata. Use before updates or ownership-sensitive actions.

NameTypeReqDescription
idnumberyesCompany ID

No output schema declared.

No examples provided.

hires_get_email_template ~37

Get full details of a specific email template by ID, including subject and body content.

NameTypeReqDescription
idnumberyesEmail template ID

No output schema declared.

No examples provided.

hires_get_evaluation ~56

Get a filled evaluation form with all answers. Returns evaluator info, summary score, summary text, and individual question answers. Use for detailed review of evaluator feedback on a candidate application.

NameTypeReqDescription
idnumberyesEvaluation form ID

No output schema declared.

No examples provided.

hires_get_form ~28

Get form details including all questions with their statuses.

NameTypeReqDescription
idnumberyesForm ID.

No output schema declared.

No examples provided.

hires_get_interview ~64

Get full details of a specific interview by ID. Use `include` to embed related candidate, application, or job data.

NameTypeReqDescription
idnumberyesInterview ID
includestringComma-separated related resources to embed: candidate, application, job

No output schema declared.

No examples provided.