Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

target_stores

Read-only

Find Target stores near a ZIP code, city/state, or lat/long, including each store's store_id for use with other Target endpoints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place": "<place>"
    },
    "name": "target_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Maximum stores to return, 1 to 20 (Target's own upstream maximum). Defaults to 20.
placeYesRequired. ZIP code, "city, state", or "latitude,longitude" to search near.
withinNoOptional. Search radius in miles, 1 to 5000. Defaults to 100.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that the result includes store_id usable with other Target endpoints, which is useful linkage context, but says nothing about pagination or result ordering. Appropriate given annotations carry the safety load.

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?

A single 24-word sentence, front-loaded with the verb and resource, with no wasted clauses. Nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With readOnly/openWorld annotations, a fully described schema, and an output schema (so returns need not be explained), the description supplies exactly what's missing: the store_id linkage for other Target endpoints. Complete for a locator tool.

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%; all three parameters (place, limit, within) are fully documented in the schema, including formats and ranges. The description only echoes the place modes, adding no syntax or default detail beyond the schema. Baseline 3 is correct.

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 names a specific verb (Find) and resource (Target stores), spells out the three input modes, and mentions the return field (store_id) for downstream use. It is readily distinguishable from the target_* shopping siblings (target_search, target_product).

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?

It states the search modes and implies this is the store-locator entry point, but does not name alternatives (e.g., target_categories) or say when not to use it. For a straightforward locator with no close competitor, this is acceptable context without exclusions.

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

All Crawlora MCP toolsInspect
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