Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indeed_job

Retrieve one Indeed job posting by its 16-character job key, returning structured details through a credential-free API with web-page fallback.

Instructions

Indeed job detail. Returns one Indeed job posting by its job key (the job_key field returned by search). Primary transport is Indeed's own credential-free GraphQL API; falls back to the original web-page transport if that fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jkYesIndeed job key (16-character hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral transparency burden. It discloses the transport mechanism (primary credential-free GraphQL API, fallback to web-page transport) and notes that no credentials are required. This is helpful context beyond the schema, though it does not cover failure modes or response structure.

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 two sentences with no redundancy. The first sentence front-loads the purpose, and the second sentence adds relevant behavioral details about transport and credentials. Every phrase earns its place.

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 simple single-parameter read-only tool with no output schema, the description is reasonably complete. It covers the input source and transport fallback, which is important for an agent to know. It does not describe return fields or error behavior, but those are less critical given the straightforward nature of the tool.

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?

The schema already provides 100% coverage by describing `jk` as an Indeed job key (16-character hex). The description adds the origin of the key (the `job_key` field returned by search), which helps the agent understand how to populate the parameter correctly, going beyond the schema's static description.

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 states clearly that the tool returns a single Indeed job posting identified by its job key. The verb 'Returns' plus the resource 'Indeed job posting' and the key reference make the purpose explicit and distinguish it from search tools like indeed_search that return multiple results.

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

Usage Guidelines4/5

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

The description implies usage after a search by referencing the `job_key` field returned by indeed_search. This is clear contextual guidance, though it does not explicitly name alternatives or state when not to use this tool. The sibling context provides additional differentiation.

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