Skip to main content
Glama

jobs

Read one job

get_job
Read-only

The full posting of one job: the employer's own text, place, pay, when it was posted, when it was last seen open, and the link to apply on the employer's site.

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

Input Schema

NameRequiredDescriptionDefault
jobYesThe job's slug or its page address, as search_jobs gives them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds real value by enumerating the returned fields, including 'when it was last seen open', which hints that a posting may no longer be live — information an agent would not get from the annotations or the one-parameter schema.

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?

One sentence, front-loaded with the core object ('the full posting of one job') followed by the field inventory. No filler and nothing deferred.

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 no output schema, the description appropriately carries the burden of describing the return content, which it does field by field. Minor gaps remain: nothing about error behavior for a missing or closed job, and no explicit routing guidance away from search_jobs.

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 single 'job' parameter is documented there as a slug or page address with the search_jobs provenance. The description adds nothing further about the parameter, so the baseline 3 applies when the schema does the work.

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 names a specific resource and scope — 'the full posting of one job' — and enumerates what the posting contains (employer text, place, pay, posted date, last-seen-open date, apply link). It distinguishes itself implicitly from a multi-result search, though the sibling search_jobs is only referenced obliquely via the parameter description rather than in this text.

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 definition makes clear this returns a single full posting, and the 'as search_jobs gives them' phrasing implies the search-then-fetch workflow. There is no explicit when-to-use/when-not statement, and no mention of behavior for stale or closed postings.

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