Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_jobs_item

Retrieve a single crawled job posting by its dataset posting ID, including seniority level and occupation fields when reliably matched; returns 404 if not found.

Instructions

Get a single posting from the jobs dataset. Returns one crawled job posting by its dataset posting id, the posting_id of a search result. Alongside the posting itself, seniority_level is entry, mid or senior, and occupation fields appear only when title and skills support a reliable match. An id not in the index returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesDataset posting id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 404 error behavior for ids not in the index and the conditional appearance of occupation fields. It is implicitly a read-only lookup, but adds no auth or rate-limit context.

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?

Three tight sentences, front-loaded with the core operation before enumerating field behaviors and the error case. Dense but each clause earns its place; no filler.

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?

For a single-param lookup with no output schema, the description conveys the essential return contents (the posting, seniority_level values, conditional occupation fields) and the failure mode. It is nearly complete, missing only explicit pagination/response-format detail that is not really applicable here.

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 the baseline is 3, but the description adds value by explaining the id's origin ('the posting_id of a search result'), which tells the agent where to source the value rather than just that it is a 'Dataset posting id'.

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?

States a specific verb ('Get') and resource ('a single posting from the jobs dataset'), and clarifies the id's provenance as 'the posting_id of a search result', which implicitly separates it from datasets_jobs_search. It stops short of naming the sibling tool or the facets/company_item variants explicitly, so differentiation is inferred rather than declared.

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 by the statement that the id comes from a search result, sketching the search-then-fetch workflow. There is no explicit when-to-use/when-not guidance or mention of alternatives such as datasets_jobs_nearby or datasets_jobs_company_item.

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

Deploy Server

Other Tools