Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

target_search

Search Target products and return products plus every filter group and option; pass option IDs back to refine results.

Instructions

Search Target products. Searches Target products and returns products plus every filter group and option available for the current result set. Pass option ids back through filter_ids as a comma-separated list. A zero total with an empty products list is a valid no-results response. The sort enum accepts relevance, featured, price-low, price-high, rating, bestselling, and newest.

Input Schema

NameRequiredDescriptionDefault
qYesProduct search query
pageNoOne-based page (1-50)
sortNoResult order
store_idNoTarget store id used for pricing
filter_idsNoComma-separated Target filter option ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "featured",
+  "price-low",
+  "price-high",
+  "rating",
+  "bestselling",
+  "newest"
+]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does reasonably well: it discloses the return contents (products plus every filter group/option), documents the no-results edge case ('a zero total with an empty products list is a valid no-results response'), and enumerates the sort values. Auth, rate limits, and pagination behavior remain undisclosed.

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?

Front-loads the core purpose and each following sentence adds distinct information (return shape, filter workflow, no-results handling, sort values). The opening is slightly redundant, restating 'Search Target products' and then 'Searches Target products' in the next clause, which is mild waste.

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?

No output schema exists, so the description must characterize the response, and it does describe both products and the filter-group structure plus the no-results case. It is largely complete for a search tool, though the two-step filter workflow could be spelled out more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the intended workflow for filter_ids (obtain option ids from the returned filter groups, then pass them back as a comma-separated list) and by restating the full sort enum, adding modest practical value over the raw 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 and resource ('Search Target products') and clarifies the return shape (products plus filter groups). It is not tautological, but it never names the differentiating sibling (e.g., target_category_products or target_product), so an agent must infer when a keyword search beats a category browse.

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?

The filter_ids round-trip ('Pass option ids back through filter_ids') implies a two-step discovery workflow, which is useful implied guidance. However, there is no explicit when-to-use versus the many other Target siblings, and no prerequisites or exclusions are stated.

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