Worklittle Jobs

Jobs · Get Job Details

get_job_details

Read-onlyIdempotent

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

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.
`location`	No	Optional location substring when resolving details by query.

Output 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.

Changed1 schema field changedOct 29, 2026

removedInput schema / properties / summary

Removed value: -{
-  "description": "If true, request first-time AI generation via GET /jobs/:id?summary=true. Default is raw plus cached AI only.",
-  "type": "boolean"
-}

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 readOnly, idempotent, non-destructive and open-world. The description adds genuinely non-obvious behavior: query-based resolution silently picks the FIRST matching live listing, which is a caveat an agent would not otherwise know. It stops short of covering ordering criteria or pagination, so not 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?

Two tight, front-loaded sentences with no filler, and the constraint on match selection comes before the fallback path. The 'Jobs — ' prefix merely echoes the title and title field, a minor redundancy.

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?

An output schema exists and the tool is a simple read with all-optional parameters, so the description only had to resolve which parameter to use — which it does well. The one remaining gap is conflicting-parameter behavior, which is unlikely but not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so 3 is the baseline, but the description goes further by explaining the precedence relationship between job_id and query and the conditional role of location — relational semantics the schema does not express. It does not clarify what happens if both job_id and query are supplied, preventing a 5.

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?

States a specific verb and resource ('Fetch detailed information about a specific job') and enumerates what detail is returned (responsibilities, qualifications, company details). It is clearly distinguishable from search_jobs, which returns listings rather than 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?

Explicitly gives both invocation paths: pass job_id when it came from search_jobs, otherwise pass query plus optional location. It even supplies a concrete example ('first software engineer job in Austin'), leaving no ambiguity about which alternative to pick.

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?