Skip to main content
Glama

Search Products By Text

products.search.text
Read-only

Search PoloPan products using a text query and optional filters. Returns products with available in-stock sizes, specifications table, shipping/return policies, pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}).

MANDATORY AGENT INSTRUCTIONS:

  1. Always tell the user the available sizes for items, and display returning & shipping policies (Negative return days = 'Exchange only |X| days').

  2. When presenting/shortlisting products, display the product specifications table.

  3. Return the base link (https://s.polopan.com/p/{handle}) during browsing. Provide the direct checkout link (https://s.polopan.com/p/{handle}/{size_index}) ONLY after the user's size is finalized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (starts at 1)
sizeNoArray of sizes to filter by, e.g. ['S', 'M', 'L', 'XL']
queryYesThe search query or style keyword to find fashion items (e.g. 'black leather jacket', 'floral summer midi dress')
genderNoTarget gender filter: 'men', 'women', or 'unisex'
vendorNoList of brand or vendor names to filter by
sort_byNoSorting criteria for the search resultsrelevance
page_sizeNoNumber of items to return per page (max 100)
price_maxNoMaximum price in local currency
price_minNoMinimum price in local currency
sort_orderNoSort order: 'asc' for ascending, 'desc' for descendingdesc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
productsYesList of matching fashion products
paginationNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the readOnly/destructive annotations by disclosing what the response contains: in-stock sizes, specifications tables, shipping/return policies, pricing, and purchase URLs. The mandatory agent instructions further clarify behavior around displaying policies, specification tables, and link handling, including the 'Exchange only |X| days' interpretation. No contradiction with annotations exists.

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?

The description is well-structured: the main purpose is stated first, followed by a clearly separated list of mandatory agent instructions. Every sentence adds operational value, and the numbered format makes the required behaviors easy for an agent to follow. There is no redundant or filler text.

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?

The description is complete for an agent to call the tool correctly: it specifies the query-based behavior, the content of results, the required user-facing disclosures, and the link policy (base link until size is finalized, then checkout link). The output schema covers return structure, and the input schema covers parameters, so no critical calling context 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?

The input schema already provides 100% parameter description coverage, so the baseline is 3. The description does not add meaningful parameter-level semantics beyond calling them 'optional filters' and mentioning the text query. Since the schema fully documents all parameters like page, size, gender, vendor, sort_by, price_min, price_max, and sort_order, the description does not need to compensate.

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?

The description clearly states the verb ('Search'), the resource ('PoloPan products'), and the method ('using a text query and optional filters'). It also enumerates exactly what is returned, making the tool's purpose unambiguous. The phrase 'text query' distinguishes it from image-based sibling tools such as products.search.image_upload and products.search.image_url.

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

Usage Guidelines4/5

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

The description clearly establishes when to use the tool: whenever an agent needs to search products by a text query. It also gives operational guidance on how to present results and when to switch from base links to checkout links. However, it does not explicitly name alternative tools or state when not to use this tool in favor of a sibling.

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.

Resources