Skip to main content
Glama

Job Description Data Extraction

extract_job_data
Read-onlyIdempotent

Extracts and converts job descriptions into structured hiring data including job title, skills, responsibilities, experience, education, and taxonomy-normalized role requirements.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_job_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
jd_textNoComplete, verbatim plain-text of the job description / job posting — every line as in the original. Do NOT summarise or base64-encode; pass raw text.
filenameNoOriginal JD filename with extension (e.g. job_description.pdf). Required when jd_base64 is provided.
jd_base64NoRaw Base64-encoded job description file content (PDF, DOC, DOCX, RTF, TXT). Provide the original filename. Use either jd_text or jd_base64, not both. Do not include a data URI prefix.

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific result payload. The exact fields depend on which tool produced this result.
metaYesRequest metadata: unique trace ID and server-side processing latency.
successNoAlways ``true`` for a successful result. Check this field first to distinguish success from error envelopes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / filename
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Original JD filename with extension (e.g. job_description.pdf). Required when jd_base64 is provided.",
      +  "title": "Filename"
      +}
    • addedInput schema / properties / jd_base64
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Raw Base64-encoded job description file content (PDF, DOC, DOCX, RTF, TXT). Provide the original filename. Use either jd_text or jd_base64, not both. Do not include a data URI prefix.",
      +  "title": "Jd Base64"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value by naming the normalized outputs ('taxonomy-normalized role requirements'), but says nothing about cost, processing latency, or failure behavior on unparseable documents — relevant given openWorldHint=true.

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?

A single front-loaded sentence with the verb and resource first, then the output inventory — no filler. The field enumeration is slightly list-heavy but every item conveys distinct output scope, so it earns its length.

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?

With an output schema present, the description need not explain return values, and 100% schema coverage handles the three optional parameters. What remains thin is the input-mode decision (paste text vs upload file) and how the tool behaves on malformed or non-JD input, but overall it is sufficient to invoke correctly.

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; each parameter already carries a rich description covering verbatim text, filename requirement, and base64 encoding rules. The tool description contributes no additional parameter meaning, so it neither gains nor loses.

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?

Uses a specific verb ('Extracts and converts') plus a specific input resource ('job descriptions') and enumerates the resulting structured fields, so an agent can tell this is JD-to-structured-data rather than resume extraction. It stops short of naming the nearest siblings (extract_resume_data, generate_jd, map_job_to_skills) to sharpen the boundary, which keeps it at 4.

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?

Usage is only implied: the description says it works on job descriptions, which tells the agent the input domain but not when to pick this over extract_resume_data (resumes) or generate_jd (creation). Notably, the schema's mutual-exclusivity rule ('Use either jd_text or jd_base64, not both') is a real usage decision the description never surfaces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources