Skip to main content
Glama

UX Jobs

Get a job listing

get_job
Read-onlyIdempotent

Return one job listing in detail — location, workplace, posted salary, employer apply link, and a description excerpt when the source provides one — by the id returned from search_jobs (or the jobs.uxjobs.io page slug). The listing URL has the complete text.

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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id from search_jobs, or the slug from a jobs.uxjobs.io/jobs/{slug}/ URL.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
logoYes
titleYes
regionYes
remoteYes
salaryYes
sourceYes
companyYes
countryYes
locationYes
apply_urlYes
posted_atYes
seniorityYes
workplaceYes
attributionYes
remote_fromYes
role_familyYes
employment_typeYes
open_confidenceYes
description_noteYes
description_excerptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / remote_from
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "title",
      -  "company",
      -  "location",
      -  "country",
      -  "remote",
      -  "workplace",
      -  "seniority",
      -  "salary",
      -  "employment_type",
      -  "posted_at",
      -  "url",
      -  "role_family",
      -  "region",
      -  "source",
      -  "open_confidence",
      -  "logo",
      -  "apply_url",
      -  "description_excerpt",
      -  "description_note",
      -  "attribution"
      -]New value: +[
      +  "id",
      +  "title",
      +  "company",
      +  "location",
      +  "country",
      +  "remote",
      +  "remote_from",
      +  "workplace",
      +  "seniority",
      +  "salary",
      +  "employment_type",
      +  "posted_at",
      +  "url",
      +  "role_family",
      +  "region",
      +  "source",
      +  "open_confidence",
      +  "logo",
      +  "apply_url",
      +  "description_excerpt",
      +  "description_note",
      +  "attribution"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "apply_url": {
      +      "type": "string"
      +    },
      +    "attribution": {
      +      "type": "string"
      +    },
      +    "company": {
      +      "type": "string"
      +    },
      +    "country": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "description_excerpt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "description_note": {
      +      "type": "string"
      +    },
      +    "employment_type": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "location": {
      +      "type": "string"
      +    },
      +    "logo": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "open_confidence": {
      +      "anyOf": [
      +        {
      +          "enum": [
      +            "verified",
      +            "unverified"
      +          ],
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "posted_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "region": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "remote": {
      +      "type": "boolean"
      +    },
      +    "role_family": {
      +      "type": "string"
      +    },
      +    "salary": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "seniority": {
      +      "enum": [
      +        "Junior / Entry",
      +        "Mid-level",
      +        "Senior",
      +        "Lead / Staff",
      +        "Principal",
      +        "Director+"
      +      ],
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "workplace": {
      +      "anyOf": [
      +        {
      +          "enum": [
      +            "remote",
      +            "hybrid",
      +            "onsite"
      +          ],
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "title",
      +    "company",
      +    "location",
      +    "country",
      +    "remote",
      +    "workplace",
      +    "seniority",
      +    "salary",
      +    "employment_type",
      +    "posted_at",
      +    "url",
      +    "role_family",
      +    "region",
      +    "source",
      +    "open_confidence",
      +    "logo",
      +    "apply_url",
      +    "description_excerpt",
      +    "description_note",
      +    "attribution"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the excerpt is conditional ('when the source provides one') and may be incomplete, with the listing URL holding the full text.

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?

A single dense sentence with the core action and payload front-loaded. The em-dash parentheticals carry real information, though the sentence is long enough that it borders on overload.

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, return values need no explanation, yet the description still usefully flags the partial-excerpt caveat and the full-text URL. Nothing essential to invoking a one-param lookup is missing.

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 the single parameter is fully documented there, including the slug form. The description restates the same id provenance without adding syntax or format detail, so the 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?

Specific verb+resource ('Return one job listing in detail') with an enumerated payload (location, workplace, salary, apply link, excerpt). It also distinguishes itself from search_jobs by naming it as the id source rather than a competing tool.

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 description establishes the acquisition path — the id comes from search_jobs or a jobs.uxjobs.io page slug — which tells the agent when this tool is applicable. It stops short of an explicit when-not-to-use or a named alternative for other lookup modes.

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