Crawlora MCP

dollartree_search

Read-only

Search Dollar Tree products or browse a category with its live filter groups and options. q is optional; browse with navigation_id from dollartree_categories or pass an exact navigation_state returned by a filter option. navigation_id and navigation_state are mutually exclusive. offset is zero-based, page_size is 48, 72, or 96, and sort accepts the storefront's exact sort values.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dollartree_search"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional. Product search query. Omit when browsing by a category or navigation state.
`sort`	No	Optional. Exact upstream sort value: empty, product.x_unitPriceNumeric\|0, product.x_unitPriceNumeric\|1, DollarProductType.new\|1, DollarProductType.averageRating\|1, product.displayName\|0, product.displayName\|1, product.casePrice\|1, or DollarProductType.numberOfReviews\|1.
`offset`	No	Optional. Zero-based upstream result offset. Defaults to 0.
`page_size`	No	Optional. Results per page: 48, 72, or 96. Defaults to 48.
`navigation_id`	No	Optional. Dollar Tree search navigation id. Use a dimension_id from dollartree_categories or an option returned in filter_groups.
`navigation_state`	No	Optional. Exact navigation_state returned for a filter option. Mutually exclusive with navigation_id; it preserves the upstream multi-filter navigation selection.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful behavioral context: results come with live filter groups whose options feed navigation_state, and pagination limits are fixed (48/72/96). It does not discuss error behavior or result caps, 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?

One dense paragraph, front-loaded with the purpose before the operational detail. Some sentences duplicate the schema's sorting and paging descriptions and could be trimmed, but nothing is filler.

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?

An output schema exists, so return values need no explanation; the description still hints that filter groups are returned for follow-up browsing. With 6 optional params all documented in schema, the agent has everything required to call it correctly.

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%, so every parameter is documented in the schema already. The description largely restates offset, page_size, and sort constraints rather than adding new meaning; the only extra signal is the mutual-exclusivity note, which the schema also carries for navigation_state. Baseline 3 applies.

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?

Opens with a specific verb and resource ("Search Dollar Tree products or browse a category") and names the two modes plus the dependency on dollartree_categories. It does not explicitly distinguish itself from nearby siblings like dollartree_keyword_typeahead or dollartree_product, so it falls short of a full 5.

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

Usage Guidelines5/5

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

Gives concrete routing: q is optional, browse with navigation_id sourced from dollartree_categories, or pass navigation_state from a filter option, and states the two are mutually exclusive. An agent knows exactly which parameter combination to use without inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?