Worklittle Jobs

Jobs · Get Job Details

get_job_details

Read-only

Jobs — Fetch detailed information about a specific job, including full responsibilities, qualifications, and company details. Pass job_id from search_jobs when you have one. If the user asks for full details of a role without an id (e.g. the first software engineer job in Austin), pass query and optional location instead — the tool loads the first matching live listing.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Role/title search used when job_id is missing (picks the first live match).
`job_id`	No	The job ID from a previous search_jobs result when available.
`summary`	No	If true, request first-time AI generation via GET /jobs/:id?summary=true. Default is raw plus cached AI only.
`location`	No	Optional location substring when resolving details by query.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`title`	No
`location`	No
`description`	No
`company_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 6, 2026

changedInput schema / properties / job_id / description

Previous value: -"The job ID from a previous search_jobs or get_recent_jobs result."New value: +"The job ID from a previous search_jobs result when available."

addedInput schema / properties / location

Added value: +{
+  "description": "Optional location substring when resolving details by query.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Role/title search used when job_id is missing (picks the first live match).",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "job_id"
-]
```

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare the tool read-only and non-destructive, so the description only needs to add behavior beyond that. It does so by disclosing the fallback behavior: when query is used, the tool loads the first matching live listing, and it notes the detail level returned. It does not cover every edge case, but the annotation coverage lowers the burden.

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?

The description is tight and front-loaded: it states the core purpose first, then gives the preferred input path, then the fallback path with a concrete example. Every sentence contributes useful guidance without redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and safety annotations, the description covers the essential decision logic for selecting and invoking the tool. It explains the two invocation modes and leaves parameter-level details to the schema, which is fully documented. Nothing critical is missing for an agent to use the tool correctly.

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 the schema already documents all four parameters meaningfully. The main description adds little that is not already in the parameter descriptions, though it reinforces the relationship between job_id and query and clarifies the fallback flow with an example. This is the expected baseline for fully documented schemas.

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?

The description clearly states the tool fetches detailed information about a specific job, naming the resource and the kind of content returned (responsibilities, qualifications, company details). It distinguishes itself from list-oriented siblings like search_jobs and get_job_keywords by emphasizing 'detailed information about a specific job' and 'full details.'

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: use job_id when available from search_jobs, or fall back to query plus optional location when the user asks for full details without an id. This directly tells the agent when to call this tool and how to supply the right inputs, including a concrete example.

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

All Worklittle 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?