Skip to main content
Glama

Metaintro Job Search

Read the job market for a search

get_market_insights
Read-onlyIdempotent

Summarize the live market for a role and place: how many openings match, the median listed pay, the most common work arrangement and the top requested skills, with how the request was understood; unfilteredConstraints lists the parts of the request that could not be applied as filters. Takes a query and the same filters as search_jobs.

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": "get_market_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
localeNo
filtersNo
commuteRadiusMilesNo
fallbackToVisitorPlaceNoWhen the query names no place and the search is not remote, search the signed-in person's saved country, or the country of an anonymous visitor's IP address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / filters / properties / companySlug
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: the response includes 'how the request was understood' and an unfilteredConstraints list of request parts that could not be applied as filters. That is a meaningful disclosure about degraded/partial matching that an agent cannot get from annotations, though freshness ('live') and any rate or cost behavior remain unstated.

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?

Front-loads the purpose and enumerates outputs in one dense but readable sentence, with the unfilteredConstraints clarification appended. No filler, though the semicolon-chained clause listing is close to over-packed and could be broken for scanability.

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?

For a complex tool with nested filters and no output schema, the description carries the return shape well: counts, median pay, work arrangement, top skills, query interpretation, and unapplied constraints. Gaps remain around currency/units for median pay, the meaning of locale, and result freshness, but an agent can invoke it correctly.

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 only 20%, with fallbackToVisitorPlace the sole documented property. The description partially compensates by declaring the filter object equivalent to search_jobs' filters and by explaining unfilteredConstraints semantics, but locale, commuteRadiusMiles, and the large nested filter set are left to the schema alone.

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?

States a specific verb ('summarize') and resource ('live market for a role and place'), then enumerates the exact outputs (match count, median listed pay, work arrangement, top skills). Naming search_jobs as the source of the same filter vocabulary cleanly separates this aggregate view from the listing tool.

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?

Says it 'takes a query and the same filters as search_jobs', which implicitly positions it alongside search_jobs, but never states the selection rule (e.g. 'use this for an overview instead of paging through search_jobs results'). No exclusions or prerequisites are given, so the when-to-use decision is left to inference.

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