Skip to main content
Glama

Get Job Title Details

get_job_title_details
Read-onlyIdempotent

Fetch the standardized job title for a Lightcast ID to normalize titles and ensure consistent career data.

Instructions

Retrieve a standardized title by its Lightcast ID.

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": {
      "title_id": "<title_id>"
    },
    "name": "get_job_title_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest
title_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that: it does not say what happens with an unknown or non-standard title ID, how the open-world lookup behaves, or what the retrieved record contains. For a lookup whose annotations carry the safety story, this one sentence contributes almost no additional behavioral context.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words, so it reads cleanly. But the brevity comes at the cost of under-specification rather than efficiency, since it omits the version parameter and any usage context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. Even so, a lookup tool with two parameters and zero schema description coverage leaves the version parameter and the not-found/error behavior entirely unaddressed. The definition is adequate enough to attempt a call but not complete enough to guide one reliably.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It does clarify that title_id is a Lightcast ID rather than a free-text title, which is genuinely useful. However, it never mentions the 'version' parameter (default 'latest'), leaving one of two parameters completely undocumented in both schema and description.

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?

The description states a specific verb and resource: 'Retrieve a standardized title by its Lightcast ID.' It makes clear this is an ID-based lookup rather than a search or normalization operation, which distinguishes it from siblings like search_job_titles or normalize_job_title. It stops short of naming any sibling explicitly, so sibling differentiation is only implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as bulk_retrieve_titles or normalize_job_title. An agent must infer from the name and the phrase 'by its Lightcast ID' that this is the single-item lookup path. Nothing is stated about what happens if the agent lacks an ID or what to do instead.

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