Skip to main content
Glama

Get a job

get_job
Read-onlyIdempotent

Full details of one job by its id from search_jobs: facts, salary, description (usually a jopp brief) and the link to the original advert.

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
idYesThe job id from search_jobs.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesThe job on jopp.ai.
roleYes
startYesAn ISO date, "immediately" or "by_agreement".
titleYes
salaryYes"stated" comes from the advert. "estimated" is a jopp estimate of the yearly salary at 100 % workload and is not from the advert.
statusYes
companyYes
applyUrlYesThe original advert: the employer's or source's page to read it in full and apply.
categoryYes
industryYes
isAgencyYes
languageYesLanguage of title and description.
workModeYes
workloadYes
educationYesLowest education the advert asks for.
locationsYes
offerKindYes
seniorityYes
experienceYesYears of experience the advert asks for.
leadershipYes
descriptionYesMarkdown. Usually jopp's brief, a factual summary of the advert; the original advert at applyUrl is authoritative.
publishedAtYes
contractTypeYes
withJoppAccountYesWhat a person can do with this job after signing in to jopp.
requiredLanguagesYes
advantageLanguagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / lastSeenAt
      Removed value: -{
      -  "description": "ISO date jopp last saw the advert online.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "url",
      -  "applyUrl",
      -  "status",
      -  "title",
      -  "company",
      -  "isAgency",
      -  "locations",
      -  "workload",
      -  "workMode",
      -  "contractType",
      -  "seniority",
      -  "offerKind",
      -  "category",
      -  "role",
      -  "industry",
      -  "start",
      -  "leadership",
      -  "education",
      -  "experience",
      -  "requiredLanguages",
      -  "advantageLanguages",
      -  "salary",
      -  "language",
      -  "description",
      -  "publishedAt",
      -  "lastSeenAt",
      -  "withJoppAccount"
      -]New value: +[
      +  "id",
      +  "url",
      +  "applyUrl",
      +  "status",
      +  "title",
      +  "company",
      +  "isAgency",
      +  "locations",
      +  "workload",
      +  "workMode",
      +  "contractType",
      +  "seniority",
      +  "offerKind",
      +  "category",
      +  "role",
      +  "industry",
      +  "start",
      +  "leadership",
      +  "education",
      +  "experience",
      +  "requiredLanguages",
      +  "advantageLanguages",
      +  "salary",
      +  "language",
      +  "description",
      +  "publishedAt",
      +  "withJoppAccount"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / offerKind / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "job",
      -      "apprenticeship",
      -      "internship",
      -      "trainee",
      -      "working_student",
      -      "freelance",
      -      "not_a_job",
      -      "unknown"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "job",
      +      "apprenticeship",
      +      "internship",
      +      "trainee",
      +      "working_student",
      +      "freelance",
      +      "taster",
      +      "not_a_job",
      +      "unknown"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / url / description
      Previous value: -"The job on getjopp.app."New value: +"The job on jopp.ai."
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the content shape (facts, salary, description, advert link), but says nothing about failure modes such as an expired or unknown id, which matters for a lookup keyed on ids pulled from a prior search.

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 tight sentence with the key information front-loaded (one job, by id, source, returned fields). The typo 'jopp brief' slightly blunts the return-value portion but does not cost much.

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?

The tool is simple (one required string parameter) and an output schema exists, so return values need not be spelled out. What remains missing is minor: behavior on invalid or expired ids.

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 coverage is 100% and the id property already documents 'The job id from search_jobs'. The description repeats that same constraint without adding format, length, or sourcing details beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('full details of one job by its id') and names the source of the id (search_jobs), which cleanly separates it from the search-style sibling. It does not address the other generic siblings like 'fetch' or 'search', but the single-job scope is unambiguous.

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 implied rather than stated: the id comes 'from search_jobs', so an agent can infer this is the follow-up call after a search. There is no explicit when-not guidance or mention of what happens with a stale/invalid id.

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