Skip to main content
Glama

Analyze a job post

analyze_job_offer

Use this only in the step-by-step path, when create_tailored_resume is unavailable or failed: analyzes a job post with the website's service (role, contract, weighted requirements) and returns an operationId to pass to tailor_resume as offerOperationId, so the job post is not analyzed twice. For a new request to tailor a resume to a job post, use create_tailored_resume instead. Pass the job post text; resolve a job URL to its text first. Do not use to judge a resume against a job; use analyze_resume_job.

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": {
      "guestToken": "<guestToken>",
      "offerText": "<offerText>"
    },
    "name": "analyze_job_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerTextYes
guestTokenYes

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the call returns an operationId that must be forwarded to tailor_resume as offerOperationId and that this prevents re-analyzing the same post, plus the input precondition that a URL must first be resolved to text. It stops short of saying what happens to the analysis server-side, but the credit-worthy context is substantial; nothing contradicts readOnlyHint=false.

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?

It is a single dense passage with no filler, though it leads with the gating condition rather than the core action and chains several clauses with commas, making it slightly harder to scan than a front-loaded what-then-when structure.

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 covers return values and annotations cover safety, and the description supplies the workflow linkage and preconditions. The one real gap is the undocumented required guestToken, which an agent needs before it can invoke the tool at all.

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 0%, so the description must carry the load. It clarifies offerText ('pass the job post text; resolve a job URL to its text first') but says nothing about guestToken, which is required, 40-100 chars, and patterned — an agent cannot infer where that token comes from.

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 pairs a specific verb and resource ('analyzes a job post') with the concrete outputs (role, contract, weighted requirements, operationId) and explicitly contrasts the tool with create_tailored_resume and analyze_resume_job, so an agent can place it precisely among its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact condition for use ('only in the step-by-step path, when create_tailored_resume is unavailable or failed'), names the preferred alternative for a new request, and adds an explicit exclusion ('Do not use to judge a resume against a job; use analyze_resume_job').

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