Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

target_search

Read-only

Search Target products and return normalized product records plus dynamic filter groups for the result set. Use target_filter_options to refine filter choices, target_category_products for a known category, or target_product for one TCIN's detail.

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": {
      "q": "<q>"
    },
    "name": "target_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesRequired. Product search query.
pageNoOptional. One-based result page, 1 to 50. Defaults to 1.
sortNoOptional. One of relevance, featured, price-low, price-high, rating, bestselling, newest.
store_idNoOptional. Positive Target store id used for pricing. Defaults to 2885.
filter_idsNoOptional. Comma-separated filter option ids returned by this response or target_filter_options.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that by stating the response includes dynamic filter groups alongside records, which signals a round-trip refinement pattern using the returned filter ids. It stops short of detailing pagination or rate-limit behavior, but those are covered in the schema.

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 tightly written sentences: the core capability first, then the disambiguation list. No filler, and the most important information is front-loaded.

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 the description need not explain return values, and it still concisely characterizes them. With annotations covering safety and the schema covering all five parameters, nothing an agent needs to select or call the tool correctly is missing.

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%, with every parameter (q, page, sort, store_id, filter_ids) documented including defaults and ranges. The description's mention of filter groups echoes what the filter_ids schema field already states, so it adds little beyond the structured data. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Search Target products') and goes further by describing the return shape ('normalized product records plus dynamic filter groups for the result set'). It also explicitly names the sibling tools it is not, so an agent can distinguish it from target_category_products and target_product 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.

Usage Guidelines5/5

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

The second sentence provides explicit routing: target_filter_options to refine filter choices, target_category_products for a known category, target_product for one TCIN's detail. Both the when-to-use and the alternatives are spelled out, leaving nothing to 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 toolsInspect
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