Skip to main content
Glama

Target products search

run_target_products_search
Read-onlyIdempotent

Search live Target products by keyword with a sort order (relevance, featured, price, rating, bestselling, newest). 1 point per returned 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": {
      "keyword": "<keyword>"
    },
    "name": "run_target_products_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: relevance = Relevance, featured = Featured, price_low = Price: low to high, price_high = Price: high to low, rating = Highest rated, bestselling = Best selling, newest = Newest
keywordYesSearch term. e.g. lego
max_itemsNoMax items (up to 500) Default: 25.
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context beyond that: the data is 'live' (freshness) and costs '1 point per returned record' (a billing/rate consideration an agent cannot infer from structured fields). It stops short of describing pagination behavior despite start_page/max_items existing.

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 with the core purpose front-loaded and no filler. The trailing cost note is terse and useful rather than padding, though the parenthetical sort list is somewhat redundant with the schema.

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?

With no output schema, the description should ideally hint at what a record contains or how pagination works, but it leaves both to inference. Annotations and the fully-covered schema carry the safety and parameter burden, so the definition is adequate but not complete for a search tool.

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 all four parameters including the sort enum are fully documented in the schema. The description restates keyword and sort but adds no syntax or format detail, and its sort list is actually less precise than the schema (says 'price' rather than the distinct price_low/price_high options). Baseline 3 is correct.

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 (Search) and resource (live Target products) plus the two axes of the operation (keyword and sort order), so an agent knows this is a keyword product-search endpoint rather than a lookup. It does not explicitly distinguish itself from siblings like run_target_products or run_target_categories_products, keeping it short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and names no alternatives, despite there being run_target_products, run_target_products_recommendations, and a host of other marketplace search tools it could be confused with. Usage is only implied by the word 'Search'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.