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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the query fallback 'loads the first matching live listing,' which tells the agent the result is a non-deterministic first-match rather than a ranked set. It does not discuss the summary/AI-generation path, though the schema covers that.

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 sentences, front-loaded with the core purpose, then the two resolution paths. The example clause is slightly verbose but earns its place by disambiguating the query path.

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 so return values need no explanation, and the description covers the calling decision fully. The one gap is silence on when to set summary=true for first-time AI generation, which matters for a tool whose default is raw-plus-cached-only.

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 including the summary generation flag. The description adds the job_id-vs-query precedence relationship, but that overlap is largely restated by the schema's own 'used when job_id is missing' note, so baseline 3 fits.

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 the payload (responsibilities, qualifications, company details), which separates it from the listing-oriented search_jobs sibling it explicitly names.

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?

Gives explicit routing rules: pass job_id from search_jobs when available, otherwise pass query plus optional location, with a concrete example ('the first software engineer job in Austin'). The two paths and the condition selecting each are spelled out rather than left to inference.

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?