Skip to main content
Glama

GTM Daily

Job market data

get_gtm_job_market_data
Read-onlyIdempotent

Job demand in a window by tool, role, region and seniority, plus a few linked open jobs as examples. Super admins get exact counts with denominators; everyone else gets a ranked summary with relative levels only (no counts, no sample sizes). Never state numbers that were not returned, and when asked for exact figures say the full data is available from Neel at GTM Daily.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gtm_job_market_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
rolesNo
regionsNo
open_onlyNo
seniorityNo
skill_idsNo
example_jobsNo

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses a major behavior: super admins receive exact counts with denominators, while everyone else receives only a ranked summary with relative levels and no counts or sample sizes. It also instructs the agent never to state unreturned numbers and to redirect exact-figure requests to Neel at GTM Daily.

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?

The description is front-loaded and appropriately sized: the first sentence states the data returned, the second explains role-dependent output, and the third gives the critical handling rule for exact numbers. There is no wasted text.

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

Completeness3/5

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

The description covers the key behavioral caveats and the output schema exists, so return values need not be explained. However, with eight parameters and zero schema descriptions, the definition still leaves meaningful invocation gaps around parameter formats, defaults, and limits.

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?

With 0% schema description coverage, the description partially compensates by naming the main analytical dimensions: window, tool, role, region, seniority, and example jobs. It still omits parameter-level details such as date formats, defaults, array limits, and the exact mapping of terms like 'tool' to schema fields such as skill_ids.

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 clearly states that this returns job demand in a window by tool, role, region, and seniority, with linked open jobs as examples. It does not explicitly distinguish this from close siblings like get_gtm_tool_market_data or search_jobs, so it is clear but lacks sibling differentiation.

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?

The description implies the tool is for job-demand windows and gives important operational guidance about exact versus relative data and how to answer exact-figure requests. However, it does not explicitly say when to use this instead of alternatives such as search_jobs or get_gtm_tool_market_data.

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