Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

target_search

Search Target products by query and return normalized results plus every filter group, option, and sort order available for that result set.

Instructions

Search Target products. Searches Target products and returns normalized 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

TableJSON 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.5/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 burden. It discloses important behaviors: returns normalized products plus all filter groups/options, filter_ids round-tripping, and that a zero total with empty products list is a valid no-results response. This goes beyond the schema and helps the agent anticipate response semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably sized and structured, but the first two sentences are redundant ('Search Target products. Searches Target products...'). The remaining sentences are focused and useful, but the redundancy could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers search behavior, filters, no-results, and sort, which is solid for a search tool. However, with no output schema, it leaves the exact structure of 'normalized products' and filter groups undefined, and pagination behavior beyond the page parameter is not explained.

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%, so the baseline is 3. The description adds value by explaining filter_ids usage and the sort enum values, but q, page, and store_id are already well-described in the schema and gain little additional meaning.

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?

The description clearly states the tool searches Target products and returns normalized products plus filter groups/options, which distinguishes it from sibling tools like target_product or target_filter_options. It uses a specific verb and resource, though it does not explicitly name alternatives.

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 description implies usage: search with a query, optionally pass filter_ids, and handle no-results. It explains the filter round-trip and sort values, but does not explicitly state when to use this tool versus target_product, target_category_products, or other Target siblings.

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