Skip to main content
Glama
HireLayer MCP server

HireLayer MCP server

Job Criteria Extractor

extract_job_criteria

Convert a job description into typed, weighted criteria—including requirement levels and optional thresholds—and store them under a job_id for resume scoring.

Instructions

Turn a job description (any language, at least 30 characters) into the typed criteria it states (usually 4 to 10, fewer for a short posting), in the posting's order, each with a criterion_id, a label, a type, a requirement (required, preferred or bonus), a weight from 0 to 3 and an optional threshold. They are written in the job's language (English, French, German, Spanish or Portuguese; English for any other) unless language says otherwise. The job is stored under job_id, so score_resumes can reuse it. Free, except a new text sent under the job_id of a job already scored: its scores are evaluated again, 1 credit each.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_text": "<job_text>"
    },
    "name": "extract_job_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoJob title.
job_idNoYour id for this job (letters, digits and . _ : ~ -, up to 200 characters). Omit it: the job is stored under an id drawn from its text.
job_textYesFull job description, as published: at least 30 characters.
languageNoLanguage of the criteria, summaries and explanations: en, fr, de, es or pt. Defaults to the language of the job's text (English when it is another).
locationNoWhere the job is based.
workspaceNoThe client company this call belongs to, when the user recruits for several companies: its HireLayer workspace id (letters, digits and . _ : ~ -, up to 200 characters), e.g. acme-corp. Jobs, resumes and scores stay apart from other clients'. A new id creates a new workspace, so reuse the exact id. Omit it for the user's default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • addedInput schema / properties / job_id
      Added value: +{
      +  "description": "Your id for this job (letters, digits and . _ : ~ -, up to 200 characters). Omit it: the job is stored under an id drawn from its text.",
      +  "pattern": "^[A-Za-z0-9._:~-]{1,200}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / job_text / description
      Previous value: -"Full job description."New value: +"Full job description, as published: at least 30 characters."
    • changedInput schema / properties / job_text / minLength
      Previous value: -1New value: +30
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Language of the criteria, summaries and explanations: en, fr, de, es or pt. Defaults to the language of the job's text (English when it is another).",
      +  "enum": [
      +    "en",
      +    "fr",
      +    "de",
      +    "es",
      +    "pt"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "Where the job is based.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Job title.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "The client company this call belongs to, when the user recruits for several companies: its HireLayer workspace id (letters, digits and . _ : ~ -, up to 200 characters), e.g. acme-corp. Jobs, resumes and scores stay apart from other clients'. A new id creates a new workspace, so reuse the exact id. Omit it for the user's default workspace.",
      +  "pattern": "^[A-Za-z0-9._:~-]{1,200}$",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say it mutates and is non-idempotent; the description adds the important context: the job is persisted under job_id (derived from text when omitted), language defaults and can be overridden, and the credit consequence of resending text under an existing job_id. It does not state failure modes or size limits beyond what the schema shows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the transformation and output shape, then moves to language, storage and cost. Dense but every clause carries information; the long enumerations of fields make it slightly heavy to scan but nothing is wasted.

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?

For a 6-parameter mutating tool with no output schema, it describes the returned criteria structure, ordering, language behavior, persistence and billing. Missing only edge-case handling (e.g., what happens to malformed or very long text, or overwriting an existing job_id's criteria), which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: job_id is a storage key that score_resumes reuses and is derived from text when omitted, and the language parameter governs the language of criteria (not just metadata). That is genuine value beyond the schema strings.

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?

States a precise verb+resource: turn a job description into typed criteria, with concrete output shape (criterion_id, label, type, requirement, weight, threshold) and count expectations (usually 4-10). This clearly distinguishes it from parse_resume (resumes), score_resumes (scoring) and search_jobs.

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?

Makes the when clear (a job description of at least 30 characters, any language) and links forward to score_resumes via job_id. It also warns about the one paid case (new text under an already-scored job_id re-scores at 1 credit each), which is real routing guidance. No explicit exclusions or named alternatives beyond that link.

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