UX Jobs

Design hiring market snapshot

hiring_snapshot

Read-onlyIdempotent

A statistical snapshot of the design job market on jobs.uxjobs.io: total open roles, roles posted in the last 7 days, remote share, and breakdowns by seniority, discipline, top countries, top cities and top hiring companies. Accepts the same optional filters as search_jobs so you can snapshot a country, a discipline or a keyword.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Keywords matched against title, company, location and description, e.g. "senior product designer fintech". All words must match.
`remote`	No	true = only fully-remote roles; false = exclude remote roles.
`company`	No	Company name (substring match).
`country`	No	ISO-3166 alpha-2 country code, e.g. "US", "GB", "DE".
`location`	No	City/state/country text to match in the posted location, e.g. "London", "New York", "Germany". Use "remote" for remote roles.
`seniority`	No	Seniority derived from the title.
`workplace`	No	Workplace arrangement when the employer stated one.
`role_family`	No	Design discipline derived from the title.
`min_salary_usd`	No	Only roles whose posted annual USD salary range reaches at least this figure. Only ~8% of roles post salary.
`employment_type`	No	e.g. "Full-time", "Contract", "Part-time", "Intern".
`posted_within_days`	No	Only roles posted in the last N days (1–60).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`countries`	Yes
`open_roles`	Yes
`top_cities`	Yes
`attribution`	Yes
`by_seniority`	Yes
`generated_at`	Yes
`top_companies`	Yes
`top_countries`	Yes
`by_role_family`	Yes
`companies_hiring`	Yes
`posted_last_7_days`	Yes
`roles_with_posted_salary`	Yes
`remote_share_of_stated_workplace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "attribution": {
+      "type": "string"
+    },
+    "by_role_family": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "by_seniority": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "seniority": {
+            "enum": [
+              "Junior / Entry",
+              "Mid-level",
+              "Senior",
+              "Lead / Staff",
+              "Principal",
+              "Director+"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "seniority",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "companies_hiring": {
+      "type": "number"
+    },
+    "countries": {
+      "type": "number"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "open_roles": {
+      "type": "number"
+    },
+    "posted_last_7_days": {
+      "type": "number"
+    },
+    "remote_share_of_stated_workplace": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "roles_with_posted_salary": {
+      "type": "number"
+    },
+    "top_cities": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "top_companies": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "top_countries": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "generated_at",
+    "open_roles",
+    "posted_last_7_days",
+    "remote_share_of_stated_workplace",
+    "roles_with_posted_salary",
+    "companies_hiring",
+    "countries",
+    "by_seniority",
+    "by_role_family",
+    "top_countries",
+    "top_cities",
+    "top_companies",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A3.9/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=false, so the safety profile is fully covered. The description adds that the tool is an aggregate over the same filter set as search_jobs, but gives no detail on caching, freshness of counts, or whether results are computed live versus pre-aggregated.

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 sentences, front-loaded with the output scope before the filter note. The enumeration is dense but earns its place by telling the agent what fields come back; only minor trimming would be possible.

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, the description need not explain return values, and the annotations cover the safety profile. Given 11 optional params and 100% schema coverage, the description plus structured fields are sufficient for correct invocation, though it never clarifies the relationship to salary_snapshot or companies_hiring.

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%, so every one of the 11 parameters is already documented in the schema, including the enum values and the ~8% salary-posting caveat. The description only says the filters match search_jobs, which adds no syntax or semantics beyond the schema; baseline 3 applies.

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+resource (statistical snapshot of the design job market) and enumerates exactly what is aggregated: totals, 7-day postings, remote share, and breakdowns by seniority, discipline, country, city, and company. This clearly distinguishes it from the listing-oriented siblings search_jobs and get_job.

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

Usage Guidelines4/5

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

The second sentence gives concrete usage context: it accepts the same optional filters as search_jobs so you can snapshot a country, discipline, or keyword. It does not, however, explicitly state when to prefer this over salary_snapshot or companies_hiring, nor any exclusions.

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

All UX Jobs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?