Skip to main content
Glama

Get a job

get_job
Read-onlyIdempotent

One job a search returned, in full: the employer's description (up to 20,000 characters), responsibilities, required and nice-to-have skills, pay and minimum years when stated, employment type, the apply link, and whether it is still open (seen on the employer's site in the last 3 days), unconfirmed, or closed.

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
idYesA job's id, as a search result gives it (8 letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, yet the description still contributes real semantics: a 20,000-character cap on employer text, which fields are present only 'when stated', and the precise meaning of the three open-status values with a 3-day freshness window. It omits error behavior for unknown or malformed ids, which keeps it from a 5.

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 front-loaded sentence opens with the core deliverable and then enumerates the returned fields, with no filler. The field list is dense but every item describes actual returned content, so nothing is wasted.

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 and a single required id, the description carries the return-value burden well by enumerating fields and defining the open/unconfirmed/closed status semantics. The only gap is what happens when the id is unknown or the job has been removed.

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?

There is one parameter with full schema coverage, and the schema already documents the 8-character id format and its origin from search results. The description adds only the implicit framing that ids come from searches, so it neither compensates for nor needs to improve on the schema.

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 states a specific resource and scope: 'One job a search returned, in full', which tells an agent this is a single-item detail fetch rather than a list or search. It never names a sibling tool explicitly, so the distinction from search_jobs or find_similar_jobs is inferred from 'a search returned' rather than stated.

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 only implied: an agent can deduce this is the follow-up call to a search that yields a job id, but there is no explicit 'use when you have an id from search_jobs' or any statement about when not to use it.

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