Retrieve Fashion Nova storefront metadata as structured JSON from Crawlora MCP; no URL parameter is required, so you can inspect the fixed Fashion Nova store details.
Get Fashion Nova store metadata. Returns storefront metadata for Fashion Nova (https://www.fashionnova.com). The storefront URL is fixed server-side, so no url parameter is accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses one useful behavioral fact — the storefront URL is fixed server-side and no url parameter is accepted — which preempts a likely caller mistake. It does not say whether the call requires auth or what fields the metadata contains, so the disclosure is partial rather than rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the verb and resource. The second sentence's restatement of "storefront metadata" is mildly redundant but adds the fixed-URL constraint.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter metadata getter with no output schema, the description covers what the tool does, which site it targets, and the parameter constraint. Only the return shape and auth expectations are unspecified, which is a minor gap at this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the schema baseline is 4. The description reinforces this by explicitly stating that no url parameter is accepted, preventing an agent from inventing one.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Get Fashion Nova store metadata") and scopes it to storefront metadata for a named domain. An agent can distinguish it from fashionnova_products, fashionnova_collections, and the other Fashion Nova siblings without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case (store-level metadata) is implied but never stated as a when-to-use condition, and no alternative sibling is named or excluded. Adequate but leaves the routing decision to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.