Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

target_stores

Find Target store locations near a ZIP code, city/state, or coordinates. Returns store IDs, addresses, phone numbers, hours, and services for use in store-specific product searches.

Instructions

Find Target stores near a location. Returns Target's physical stores near a ZIP code, a free-text "city, state", or a "latitude,longitude" pair, including each store's store_id, status, distance, phone, address, service list, time zone, and two weeks of daily opening hours. Use the returned store_id values with the store_id parameter on target-search, target-category-products, target-filter-options, and target-product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum stores to return (1-20)
placeYesZIP code, city/state, or latitude,longitude
withinNoSearch radius in miles (1-5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses accepted location formats, the fact that only physical stores are returned, and a detailed list of returned fields including two weeks of opening hours. It does not cover defaults, error behavior, or auth/rate limits, but the read-only search nature is clear.

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?

Three sentences, with the main purpose first and every sentence contributing input formats, output content, or downstream usage. There is no filler or repetition of structured metadata.

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 store-locator tool with no output schema, the description covers accepted inputs, output fields, and how to chain results into sibling tools. Minor gaps like default limit/within behavior and no-store/error handling keep it from a perfect score.

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%, so the baseline is 3. The description restates the place formats already in the schema and adds downstream context, but it does not materially enhance the semantics of limit or within beyond their schema descriptions.

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 opens with a specific verb and resource ('Find Target stores near a location') and defines accepted input formats and output fields. It also distinguishes itself from sibling Target tools by explaining that returned store_id values feed into target-search, target-category-products, target-filter-options, and 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?

The description gives clear usage context: it is a store locator whose returned store_id values should be passed to several named sibling tools. It does not explicitly state exclusions or when to prefer a sibling instead, but the downstream-use sentence provides actionable guidance.

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