Skip to main content
Glama

get_job_trends

Read-onlyIdempotent

Reveal hiring trends, demand velocity, and top skills for a role or location to guide job search and skill planning.

Instructions

Get hiring trends, demand velocity, and top demanded skills by role/location.

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": {
      "kw": "<kw>"
    },
    "name": "get_job_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
kwYesTarget role or skill (e.g. 'Python Backend', 'Cloud Architect')
locNoTarget location (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.8
    • addedInput schema / properties / kw / description
      Added value: +"Target role or skill (e.g. 'Python Backend', 'Cloud Architect')"
    • addedInput schema / properties / loc / description
      Added value: +"Target location (optional)"
  2. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context beyond that, such as data recency, aggregation window, or whether openWorld means external market data is pulled live.

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

Conciseness5/5

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

A single front-loaded sentence that names the verb, the three returned metrics, and the two dimensions of scope. Nothing is padded and nothing needs to be moved earlier.

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 and rich annotations, the description need not explain return values, and it correctly states what the tool produces. The remaining gap is routing guidance against the overlapping trend/industry tools, which is a minor omission for a two-parameter read tool.

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 description coverage is 100% and both parameters (kw, loc) are documented with examples and an optional default, so the schema carries the parameter burden. The description only restates the role/location dimension without adding format or matching semantics, making the baseline 3 appropriate.

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 pairs a specific verb ('Get') with a concrete set of outputs (hiring trends, demand velocity, top demanded skills) scoped by role/location. It is clearly distinguishable from job-search siblings like search_jobs, though it does not explicitly separate itself from the industry-analysis siblings (deep_industry_analysis, get_industry_insights).

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 by the content: an agent can infer this is the tool for trend/demand questions rather than listings or salaries. There is no explicit when-to-use statement, no exclusion of the overlapping industry-analysis tools, and no stated prerequisites.

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