Skip to main content
Glama

Search Job Titles

search_job_titles
Read-onlyIdempotent

Search standardized job titles by query to find matching titles and choose a taxonomy version. Use it to map or normalize role names for career and skills analysis.

Instructions

Search standardized job titles. version is a Titles taxonomy version or latest.

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": {
      "query": "<query>"
    },
    "name": "search_job_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
versionNolatest

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results come from a standardized Titles taxonomy and that versioning exists, but says nothing about matching behavior (exact vs partial), result ordering, or how limit truncates results.

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?

Two short sentences, front-loaded with the action and resource, with no filler. The second sentence is grammatically terse to the point of being cryptic, 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?

An output schema exists, so return values need not be described. However, for a search tool with zero parameter documentation, the absence of any note on how 'query' is matched and how results are ranked leaves a meaningful gap for correct invocation.

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% across three parameters, so the description must carry the load and largely does not. It explains only 'version' (a Titles taxonomy version or 'latest'), which mostly restates the schema default, while 'query' matching semantics and 'limit' behavior (default 10, max 100) are left unexplained.

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 gives a specific verb and resource ("Search standardized job titles"), which tells an agent this operates on a taxonomy of titles rather than on postings. It does not differentiate from siblings such as normalize_job_title, get_job_title_details, or bulk_retrieve_titles, so an agent must infer which title-oriented tool fits.

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 exclusions, and no named alternative. The only contextual sentence concerns the version parameter, leaving the agent to guess whether this tool is for lookup, autocomplete, or resolution of a known title.

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