Skip to main content
Glama

search_products

Search for fashion products on Klydo. Use optional filters for category, gender, and price range to narrow results.

Instructions

Search for fashion products on Klydo.

Args: query: Search terms (e.g., "black dress", "nike shoes", "cotton kurta") category: Filter by category (e.g., "dresses", "shoes", "tshirts", "kurtas") gender: Filter by gender ("men" or "women") min_price: Minimum price in INR (e.g., 500) max_price: Maximum price in INR (e.g., 2000) limit: Maximum number of results (default 10, max 50)

Returns: List of matching products. Each product has: - image_url: Direct CDN image link (always show this) - url: Buy link on klydo.in (may be null — only show when present) - price, brand, name, category

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
categoryNo
genderNo
min_priceNo
max_priceNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses return structure, null conditions for url, and search behavior. Adequate for a read-only search tool.

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?

Well-structured with Args and Returns sections, front-loaded with purpose. Every sentence is informative, no fluff. Concise yet comprehensive.

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?

Output schema exists and description explains return fields thoroughly. Covers all aspects of a search tool with multiple filters. Complete and self-contained.

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

Parameters5/5

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

Schema has 0% description coverage on parameters. Description compensates fully with detailed explanations, examples, and defaults for each of the 6 parameters, adding significant meaning beyond the schema.

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?

Description clearly states tool searches for fashion products on Klydo, with specific examples. Distinguishes from sibling tools like get_product_details and get_trending by focusing on search.

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?

Description provides clear usage context with examples for each filter parameter. Lacks explicit when-not or alternative tool guidance, but sufficiently implies search vs details/trending.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/myselfshravan/klydo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server