Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indeed_locations_suggest

Fetch Indeed location-search autocomplete suggestions from partial location text to build a valid l value for search. Returns up to 25 matches via Crawlora MCP.

Instructions

Indeed location suggestions. Returns Indeed's own location-search autocomplete suggestions for a partial location string -- the same suggestions the app's search bar offers -- for building a valid l value for search.

Input Schema

NameRequiredDescriptionDefault
qYesPartial location text
limitNoMax suggestions to return, defaults to 10, maxes at 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that this is a read-only autocomplete service returning the platform's own suggestions, but says nothing about rate limits, auth requirements, response shape, or behavior on empty/no-match input. Adequate but incomplete for a zero-annotation tool.

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?

Single tightly-packed sentence, front-loaded with what it returns and followed by the purpose. The title-phrase 'Indeed location suggestions' is mildly redundant with the verb that follows, preventing a 5, but there is no wasted verbosity.

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 two-parameter suggest tool with no annotations and no output schema, the description explains both the input nature (partial string) and the intended downstream use (`l` value). Returning the suggestions is described adequately; only richer behavioral detail is missing.

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 coverage is 100% (both `q` and `limit` are documented in the schema). The description's 'partial location string' mirrors the schema's 'Partial location text' and adds no new syntax, format, or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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 ('Returns Indeed's own location-search autocomplete suggestions'), and pins down the scope ('for a partial location string'). The added detail that these match the app search bar and feed the `l` parameter makes it unmistakably distinguishable from siblings like indeed_search or indeed_job.

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 clause 'for building a valid `l` value for search' clearly conveys the intended workflow (call this before search to obtain a location value), which is real when-to-use guidance. It does not, however, name an explicit alternative or state when-not to use it, so it stops short of 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