Crawlora MCP

dollartree_products

Read-only

Get complete Dollar Tree product records for comma-separated product_ids returned by dollartree_search. This mirrors the storefront's list-valued productIds request; use dollartree_product for a single record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_ids": "<product_ids>"
    },
    "name": "dollartree_products"
  }
}

Input Schema

Name	Required	Description	Default
`product_ids`	Yes	Required. Comma-separated Dollar Tree product repository ids returned by dollartree_search.

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 2, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered by structured data. The description adds that records are 'complete' and that the request mirrors the storefront's list-valued productIds parameter, which is mild extra context but doesn't cover batching limits, error behavior for invalid/missing ids, or partial results. Adequate but not rich.

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?

Two sentences, front-loaded with the action and scope, then the alternative routing. No filler, no repetition of schema text beyond what is needed to name the parameter.

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?

An output schema exists, so return values need not be explained, and the single required parameter is fully documented. What is missing is how the tool behaves on bad or unknown ids and whether there is a cap on id count, which for a batch fetch would be useful; otherwise the definition is complete for correct invocation.

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 coverage is 100% and the schema property already says 'Comma-separated Dollar Tree product repository ids returned by dollartree_search'. The description repeats the comma-separated framing without adding format, delimiter handling, or limit details, so baseline 3 applies.

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?

States a specific verb and resource ('Get complete Dollar Tree product records') and scopes it to comma-separated product_ids. It also names the sibling dollartree_product and explains the difference (single record vs. list), so an agent can distinguish them immediately.

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?

Explicitly says the ids come from dollartree_search and directs single-record lookups to dollartree_product. That is an explicit when-to-use and when-to-use-something-else statement, which is the top of the scale.

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?