Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_store

Retrieves normalized storefront metadata for Fashionphile from credential-free Shopify JSON, fixing broken /products.json access via fallback domains or embedded page data.

Instructions

Get Fashionphile store metadata. Returns normalized storefront metadata for Fashionphile (https://www.fashionphile.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.17.5

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it reveals the credential-free source, normalized metadata output, fixed URL, and concrete fallback behavior when `/products.json` is blocked. This is more than most tool descriptions disclose.

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 dense sentences with no filler. The purpose is front-loaded, followed by the data source and then the fallback behavior; every sentence adds necessary information.

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 tool with no output schema, the description covers everything an agent needs: what it returns, where the data comes from, the fixed scope, and fallback behavior. It is complete enough to invoke correctly without further inference.

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 schema has zero parameters and 100% coverage, so the baseline is already high. The description adds important negative semantics by explicitly stating that no `url` parameter is accepted and that the URL is fixed server-side, preventing an agent from trying to pass one.

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: 'Get Fashionphile store metadata.' It further distinguishes the tool as a 'brand-pinned wrapper around the generic Shopify store family,' separating it from both the generic store family and the many fashionphile_* sibling tools focused on pages, products, and collections.

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 clearly states the tool is a fixed-scope store-metadata endpoint and explains that no `url` parameter is accepted because the storefront URL is server-side. It does not explicitly name alternatives or say when to prefer other fashionphile_* tools, but the context is sufficient for correct selection.

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