Skip to main content
Glama

Search Products By Text

products.search.text
Read-only

Search fashion products by text keyword and filter by size, gender, price, or vendor. Get in-stock items with specs, pricing, and purchase links.

Instructions

Search PoloPan catalog products using a text keyword query with optional multi-attribute filters. Returns matching fashion items with available in-stock sizes, product specifications, shipping/return policies, discounted pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}).

PURPOSE & DISAMBIGUATION:

  • Primary text-based catalog search tool for fashion discovery across apparel, footwear, and accessories.

  • Distinct from 'products.search.image_url' / 'products.search.image_upload': Use this tool for textual queries and keyword filters, NOT for visual image search.

  • Distinct from 'products.search.alternatives': Use this tool for open discovery queries, NOT for finding direct visual substitutes of a known product handle.

  • Distinct from 'looks.curation.by_occasion': Use this tool to search individual products, NOT complete multi-piece outfit looks.

WHEN TO USE:

  • When a user searches for clothing or fashion styles using keywords, brand names, colors, or categories (e.g. 'black leather jacket', 'floral summer midi dress', 'men linen shirts').

  • When refining catalog searches with structured filters like price ranges, gender, sizes, or vendor brands.

WHEN NOT TO USE:

  • Do NOT use when the user provides an image URL or image file (use 'products.search.image_url' or 'products.search.image_upload').

  • Do NOT use when searching for cheaper/higher-end substitutes of a specific known product (use 'products.search.alternatives').

  • Do NOT use to find curated complete occasion outfits (use 'looks.curation.by_occasion').

BEHAVIOR & SAFETY:

  • Read-only and idempotent with no persistent state modifications.

  • Automatically sanitizes and enriches product records with verified PoloPan short permalinks (https://s.polopan.com/p/{handle}), computed in-stock size lists, and human-readable shipping and return policy strings.

  • Handles pagination and multi-attribute filtering deterministically.

PARAMETERS & CONSTRAINTS:

  • 'query' (string, required): Free-text search query or style keyword (e.g. 'black linen shirt', 'oversized hoodie').

  • 'page' (integer >= 1, default 1): Pagination page number.

  • 'page_size' (integer 1-100, default 20): Number of products returned per page.

  • 'sort_by' (enum, default 'relevance'): Ranking criterion ('relevance', 'price', 'title').

  • 'sort_order' (enum, default 'desc'): Sort direction ('asc' for ascending, 'desc' for descending).

  • 'gender' (string, optional): Target demographic filter ('men', 'women', or 'unisex').

  • 'size' (array of strings, optional): Size filter array (e.g. ['S', 'M', 'L', 'XL', '32', '40']).

  • 'price_min' (number, optional): Minimum price threshold in local currency.

  • 'price_max' (number, optional): Maximum price threshold in local currency.

  • 'vendor' (array of strings, optional): List of brand or vendor names to filter by.

MANDATORY AGENT INSTRUCTIONS:

  1. Always communicate available in-stock sizes, fast dispatch SLA, and return policy for each product (Negative return days = 'Exchange only |X| days').

  2. When presenting or shortlisting products, display the product specifications table (Fabric, Pattern, Collar, Sleeves, Fit, Care).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPagination page number (1-indexed, starts at 1)
sizeNoArray of size labels to filter by (e.g. ['S', 'M', 'L', 'XL', '32'])
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 (e.g. ['Zara', 'H&M', 'Tandul'])
sort_byNoSorting criteria for search results: 'relevance', 'price', or 'title'relevance
page_sizeNoNumber of items to return per page (1 to 100, default 20)
price_maxNoMaximum price in local currency
price_minNoMinimum price in local currency
sort_orderNoSort order: 'asc' for ascending, 'desc' for descendingdesc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.5

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the readOnlyHint/destructiveHint annotations by stating the tool is read-only and idempotent, and by disclosing enrichment behaviors: sanitizing records, computing in-stock size lists, generating verified permalinks, and adding shipping/return policy strings. It also notes deterministic pagination and filtering, giving the agent a clear behavioral model.

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?

The description is well-structured with clear headers, front-loaded purpose, and effective disambiguation, making the length justifiable for a tool with 10 parameters and many siblings. However, the 'PARAMETERS & CONSTRAINTS' section largely duplicates the input schema, and the mandatory agent instructions, while useful, are presentation guidance rather than selection-critical content.

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?

Even without an output schema, the description states exactly what the tool returns: matching products, in-stock sizes, specifications, policies, prices, and verified purchase URLs. It also gives agent-facing instructions for presenting results and handling checkout links, covering the operational context an agent needs beyond the schema.

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 the schema already documents every parameter thoroughly. The description's parameter section largely repeats schema information, though it adds useful examples and clarifies constraints like sort defaults. This is a solid baseline case where the schema carries the load and the description adds only marginal value.

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 opens with a specific verb and resource: 'Search PoloPan catalog products using a text keyword query.' It further disambiguates from three sibling tools by naming them and contrasting text search against image search, alternatives, and occasion-look curation. An agent can reliably select this tool based on the stated purpose alone.

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?

Dedicated 'WHEN TO USE' and 'WHEN NOT TO USE' sections give explicit conditions with concrete examples such as 'black leather jacket' and name the exact sibling tools to use instead for image, substitute, or outfit queries. This leaves no ambiguity about when to invoke this tool versus alternatives.

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