Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

amazon_jobs_search

Search Amazon's public careers site by keyword or job category to retrieve full job descriptions and qualifications inline. Sort results by relevance or newest posting.

Instructions

Amazon Jobs search. Searches Amazon's public careers site (amazon.jobs). Each result includes the full description and qualifications inline. sort accepts relevant (default, relevance ranking) or recent (newest posted first). Either q or category (or both) must be given -- category filters by Amazon's own job-category taxonomy and works with no text query at all. See amazon-jobs-categories for the full, live-verified list of accepted category values.

Input Schema

NameRequiredDescriptionDefault
qNoSearch query. Either q or category is required
pageNoPage number, 1-based
sortNoSort order
limitNoResults per page, max 100 (default 20)
countryNoISO 3166-1 alpha-3 country code filter
categoryNoAmazon's own job-category taxonomy slug, case-insensitive. Either q or category is required

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • changedInput schema / properties / category / description
      Previous value: -"Amazon's own job-category taxonomy slug. Either q or category is required"New value: +"Amazon's own job-category taxonomy slug, case-insensitive. Either q or category is required"
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "administrative-support",
      +  "applied-science",
      +  "audio-video-photography-production",
      +  "business-intelligence",
      +  "business-merchant-development",
      +  "buying-planning-instock-management",
      +  "corporate-operations",
      +  "customer-service",
      +  "data-science",
      +  "database-administration",
      +  "design",
      +  "economics",
      +  "editorial-writing-content-management",
      +  "facilities-maintenance-real-estate",
      +  "finance-accounting",
      +  "fulfillment-associate",
      +  "fulfillment-operations-management",
      +  "fulfillment-warehouse-associate",
      +  "hardware-development",
      +  "human-resources",
      +  "investigation-loss-prevention",
      +  "leadership-development-training",
      +  "legal",
      +  "machine-learning-science",
      +  "marketing-pr",
      +  "medical-health-safety",
      +  "operations-it-support-engineering",
      +  "procurement",
      +  "project-program-product-management-non-tech",
      +  "project-program-product-management-technical",
      +  "public-policy",
      +  "public-relations",
      +  "research-science",
      +  "sales-advertising-account-management",
      +  "software-development",
      +  "solutions-architect",
      +  "supply-chain-transportation-management",
      +  "systems-quality-security-engineering"
      +]
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "relevant",
      +  "recent"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully notes that results embed full descriptions and qualifications and that `recent` means newest-posted-first, but says nothing about authentication, rate limits, or pagination depth beyond the schema's page/limit fields.

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?

Four compact sentences, all front-loaded with the core purpose and the required-parameter constraint, then the sort semantics and the pointer to the category-list tool. Nothing is redundant with the schema.

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?

No output schema exists, so the description compensates by telling the agent results include full descriptions and qualifications inline, and it covers the q/category requirement and sort options. It does not discuss pagination behavior or result caps, which the schema only partially implies.

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. The description adds genuine meaning beyond the schema: `relevant` is the default relevance ranking, `recent` sorts newest-first, and `category` operates with no text query, clarifying the required q/category constraint that the schema alone only repeats.

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 and resource ('Amazon Jobs search', 'Searches Amazon's public careers site') and notes results include full descriptions and qualifications inline, which separates it from the amazon_jobs_job detail sibling. It does not explicitly name that sibling or contrast with the other jobs_* search tools, so it falls short of a 5.

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?

Gives concrete when-to-use guidance: 'Either `q` or `category` (or both) must be given', '`category` works with no text query at all', and routes the agent to `amazon-jobs-categories` for accepted category values. No explicit when-not-to-use or alternative-tool routing, so not a 5.

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