Skip to main content
Glama

家具・家電・ガジェット商品を検索

search_products

Search furniture and home products across 31 categories using keywords, dimensions, price, color, or brand. Get purchase guidance, accessory recommendations, and affiliate links.

Instructions

ユーザーが「棚が欲しい」「Dysonのドライヤー」「幅40cmに入るもの」と言ったときに呼ぶ。31カテゴリ・80+ブランドのカタログをキーワード・サイズ(mm)・価格・色・ブランドで横断検索。結果にrelated_items_hintがある場合はget_related_itemsで付属品チェーンを取得できる。buy_guideがある場合はbest_for/avoid_ifをユーザーに伝えて購入判断を助けること。seasonal_hints/active_salesがある場合はセール情報を伝えること。色はエイリアス対応(白→ホワイト/アイボリー等)。各商品のaffiliate_urlをユーザーに提示すること。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYes【必須】検索目的
keywordNoキーワード(商品名・ブランド・タグで部分一致、スペース区切りでAND検索)
width_mm_minNo幅の最小値(mm)
width_mm_maxNo幅の最大値(mm)
height_mm_minNo高さの最小値(mm)
height_mm_maxNo高さの最大値(mm)
depth_mm_minNo奥行きの最小値(mm)
depth_mm_maxNo奥行きの最大値(mm)
price_maxNo価格の上限(円)
price_minNo価格の下限(円)
colorNo色(例:ホワイト、白、ブラウン、木目)。エイリアス対応:白→ホワイト/アイボリー等
categoryNoカテゴリ(例:デスク、美容家電、スマートホーム)
brandNoブランド(例:ニトリ、IKEA、Dyson、Panasonic)
in_stock_onlyNo在庫ありのみ(デフォルト:true)
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining color alias handling, result structure hints (related_items_hint, buy_guide, seasonal_hints), and the requirement to present affiliate_url. It doesn't mention rate limits, authentication needs, or pagination behavior, but covers most operational aspects.

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?

Front-loaded with usage examples, then explains search scope and filters, then result handling instructions. Every sentence adds value, though it's slightly dense. Could be more structured with bullet points but remains efficient.

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

Completeness4/5

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

For a complex search tool with 14 parameters and no output schema, the description does well by explaining result structure and next-step actions. It covers the main behavioral aspects but doesn't mention error handling, result limits, or sorting options. Given the rich parameter schema and sibling context, it's mostly complete.

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 baseline is 3. The description adds some context about color aliases and keyword search behavior (partial match, space-separated AND), but doesn't significantly enhance parameter understanding beyond what the schema already provides.

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 tool searches across 31 categories and 80+ brands using keywords, dimensions, price, color, and brand. It distinguishes from siblings like search_amazon_products or search_rakuten_products by specifying it searches a specific catalog, and from get_product_detail by being a search rather than detail retrieval tool.

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?

Explicitly provides usage examples ('when user says...'), mentions when to use sibling tools (get_related_items for accessories), and gives guidance on how to handle specific result fields (buy_guide, seasonal_hints, affiliate_url). It clearly distinguishes this from other search tools by specifying the catalog scope.

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/ONE8943/ai-furniture-hub'

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