Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shop_app_shop

Retrieve a Shop.app merchant profile by handle, including name, description, logo, banner, rating, review count, storefront and Shop.app URLs, and collection summaries.

Instructions

Get Shop.app shop. Returns a Shop.app merchant profile by shop handle: name, description, logo, banner, rating, review count, storefront and Shop.app URLs, and collection summaries when the shop page lists them. Unknown handles return an error.

Input Schema

NameRequiredDescriptionDefault
handleYesShop handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden, and it does add real behavior: collection summaries are returned only 'when the shop page lists them' (conditional content) and 'Unknown handles return an error' (error semantics). It omits auth requirements, rate limits, and pagination, keeping it short of full transparency.

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 tight sentences, front-loaded with purpose then returned content then error behavior. No filler, and each sentence earns its place.

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 output schema, the description usefully enumerates the returned fields and the error case, which carries most of the return-value burden. It is largely complete for a one-param read tool, though it lacks any note on pagination or auth that could matter operationally.

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% for the single required 'handle' parameter, so the schema already documents it. The description mentions the lookup key ('by shop handle') but adds no format, casing, or example detail beyond the schema, matching the baseline 3.

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 (Get) and resource (Shop.app shop / merchant profile) and enumerates the concrete fields returned, so an agent can tell this is the merchant-profile lookup. However, it never names or contrasts with sibling tools like shop_app_product or shop_app_shop_products, leaving sibling differentiation implicit.

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?

Usage is only implied: you look up a merchant by handle and unknown handles error. There is no explicit when-to-use vs when-not guidance nor any pointer to alternatives such as shop_app_search for discovery or shop_app_shop_products for a shop's inventory.

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