Skip to main content
Glama

Analyze Job Description

getmattered_analyze_job_description

Extracts and categorizes keywords and requirements from a pasted job description, marking must-haves and importance, so you can tailor a resume or application.

Instructions

Extracts the keywords and requirements of a pasted job description, each with a category and an importance, with must-haves marked. getmattered_score_resume compares a resume with a posting. Changes nothing on the account. Uses AI credits.

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_description": "<job_description>"
    },
    "name": "getmattered_analyze_job_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_descriptionYesFull text of the job description

Output Schema

NameRequiredDescriptionDefault
keywordsYes
setupStepNoPresent while account setup is open: the first setup step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.13.2
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Addedv1.9.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations it discloses two behaviors an agent cannot see in structured data: it consumes AI credits and it does not persist changes to account data. That is useful cost/side-effect context. The statement "Changes nothing on the account" sits in mild tension with readOnlyHint=false, but it is best read as a narrower claim (no account mutation) rather than a direct contradiction.

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?

Four short, front-loaded sentences with no filler; the core extraction purpose comes first and the sibling routing second. The stylized sentence fragments ("Uses AI credits.") are efficient but slightly telegraphic, keeping it out of top marks.

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?

An output schema exists, so the description does not need to detail return values, and it still sketches the result shape enough to set expectations. For a one-parameter tool with annotations, the main remaining gap is the magnitude of credit cost and whether the pasted text is retained, but nothing critical to correct invocation is missing.

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?

With a single parameter and 100% schema description coverage, the schema already documents job_description as the full text. The description adds only the word "pasted," implying raw pasted text rather than an ID or URL, and says nothing about the 50–50000 character bounds or what happens on truncation, so baseline 3 applies.

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?

Names a specific verb and resource ("Extracts the keywords and requirements of a pasted job description") and even describes the shape of the output (category, importance, must-haves marked). It explicitly distinguishes itself from getmattered_score_resume, so an agent can route between the two without opening either schema.

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?

The contrast sentence "getmattered_score_resume compares a resume with a posting" gives a clear selection rule: use this one to analyze a posting alone, that one to compare against a resume. There are no explicit exclusions (e.g., when a posting is too short or already analyzed), which keeps it just below a 5.

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