Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shop_app_shop_locations

List public Shop.app retail locations by shop handle, returning address, latitude/longitude, total count, and next-page cursor.

Instructions

List Shop.app shop locations. Returns the public retail locations of a Shop.app merchant by shop handle, up to limit (default 10, max 50). Each location has its id, name, latitude and longitude, and street address; the response also carries the total count and a cursor for the next page. A shop with no public retail locations returns an error.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum locations, defaults to 10 and supports up to 50
handleYesShop handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it delivers: it enumerates returned fields (id, name, latitude/longitude, street address), discloses pagination via a next-page cursor and total count, and explicitly documents the error case for a shop with no public retail locations. Auth requirements are the only notable omission.

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, each earning its place, and correctly front-loaded: purpose, then return shape, then pagination, then the edge-case error. Zero filler.

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?

With no annotations and no output schema, the description still covers return fields, pagination, and error behavior, which is close to sufficient for a simple two-parameter listing tool. It stops short of describing handle format or how to obtain a handle.

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%, so the schema already documents both parameters. The description restates the limit default/max and clarifies handle as the shop identifier, which adds only marginal value over structured data. Baseline 3 is appropriate.

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 gives a specific verb and resource ('List Shop.app shop locations') plus the routing key ('by shop handle'). This distinguishes it cleanly from siblings like shop_app_shop_products and shop_app_shop_reviews, so an agent can route without opening the schema.

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

Usage Guidelines3/5

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

The requirement of a shop handle implies the precondition for use, but the description never states when to prefer this over sibling tools such as shop_app_shop or where location data sits in the broader flow. Usage is implied rather than stated.

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