Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_store

Fetch normalized Oh Polly storefront metadata from credential-free JSON, returning clean store data for product and shop analysis.

Instructions

Get Oh Polly store metadata. Returns normalized storefront metadata for Oh Polly (https://www.ohpolly.com), sourced from credential-free storefront JSON. This endpoint is a brand-pinned wrapper around the generic Shopify store family: the storefront URL is fixed server-side, so no url parameter is accepted. If the vanity domain blocks /products.json, the service may fall back to a public *.myshopify.com domain discovered from the storefront page, or to the storefront's own embedded page data for storefronts that expose neither.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does it well: it notes the endpoint is credential-free, the URL is fixed server-side so no url parameter is accepted, and it details fallback behavior when /products.json is blocked. It doesn't cover failure modes or rate limits, so not a 5.

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?

The description is well-structured and front-loaded with the purpose, then adds source and fallback context. Minor redundancy exists between 'Get Oh Polly store metadata' and 'Returns normalized storefront metadata for Oh Polly', so not a perfect 5.

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?

For a zero-parameter, brand-pinned metadata endpoint, the description is complete: it identifies the brand, source, credential requirement, parameter constraint, and fallback strategy. Nothing an agent needs to decide to call it or to understand its behavior is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, so the baseline is 4. The description goes further by explicitly stating that no url parameter is accepted and explaining why (fixed server-side URL), preempting a likely mistake given the sibling shopify_store tool may accept a url. This adds clear value beyond the empty schema.

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 states a specific action ('Get Oh Polly store metadata') and resource (Oh Polly storefront metadata at https://www.ohpolly.com). It also frames the tool as a 'brand-pinned wrapper around the generic Shopify store family', immediately distinguishing it from sibling shopify_store and other brand store endpoints. The scope is unambiguous.

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 provides clear context by positioning the endpoint as a brand-pinned wrapper with a server-side fixed URL, implying it is the Oh Polly-specific alternative to the generic Shopify store tool. However, it does not explicitly name an alternative endpoint or state when not to use it, so it stops short of full exclusion 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