Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dollartree_products

Fetch complete public product records for a comma-separated list of Dollar Tree product IDs, returning structured JSON that matches the storefront's list-valued productIds resource.

Instructions

Get multiple Dollar Tree product records. Returns the complete public product records for a comma-separated list of Dollar Tree repository ids, matching the storefront's list-valued productIds resource.

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

NameRequiredDescriptionDefault
product_idsYesComma-separated Dollar Tree product ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that complete public records are returned and that this mirrors the storefront's list-valued productIds resource, but it omits ordering guarantees, behavior for unknown/missing ids, and any cap on the number of ids accepted.

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?

Two compact sentences that are front-loaded with the action and return content; no filler. Slightly repetitive in restating the id list twice ('comma-separated list' and 'list-valued productIds resource').

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?

For a one-parameter read tool with no output schema, the description covers what it does and what comes back. The main residual gap is batch-size and error handling, which an agent would need before calling with large id lists.

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 the single product_ids parameter is already documented. The description restates the comma-separated format and frames ids as repository ids matching the storefront resource, adding only marginal meaning beyond the schema.

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?

States a specific verb ('Get') and resource ('multiple Dollar Tree product records') and scopes it to a batch of repository ids. The word 'multiple' contrasts with the singular dollartree_product sibling, though the description never names that alternative explicitly.

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

Usage Guidelines3/5

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

Use when you have a comma-separated list of ids is implied by the phrasing, but there is no explicit when-to-use versus dollartree_product / dollartree_search, no stated exclusions, and no guidance on batch size limits.

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