Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ikea_search

Search IKEA products by free-text query or item number, returning names, prices, ratings, images, colors, and variants for a selected country and language.

Instructions

Search IKEA products. Searches IKEA products and returns name, price, rating, images, colors, and variant data. q is a free-text query; an IKEA item number also resolves as its own single result. country and language select IKEA's per-country site (default us/en). A zero total with an empty products list is a valid no-results response.

Input Schema

NameRequiredDescriptionDefault
qYesFree-text product search query
sizeNoResult count (1-100)
countryNoLowercase 2-letter IKEA site country code
languageNoLowercase 2-letter IKEA site language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers useful context: the returned fields, the item-number shortcut, the default us/en site selection, and the clarification that a zero total with an empty products list is a valid no-results response. It omits auth/permission needs and any pagination nuance, so it is not exhaustive.

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 the core action, then progressively narrowing to query semantics, locale handling, and the no-results case. Slightly redundant in restating 'Search IKEA products' twice, but overall tight and well ordered.

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?

No output schema exists, and the description compensates by listing the return fields and the no-results shape. Combined with locale defaults and query semantics, an agent has enough to call this correctly, though a note on size/pagination behavior would round it out.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: q accepts free-text or a resolvable IKEA item number, and country/language select IKEA's per-country site with a default of us/en. That is more than the schema alone conveys.

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?

The description uses a specific verb+resource ('Search IKEA products') and enumerates what comes back (name, price, rating, images, colors, variants). It does not name or contrast against likely siblings like ikea_product or ikea_suggest, so it falls short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'search' and the note that an item number resolves as a single result, but there is no explicit when-to-use/when-not guidance or routing to alternatives such as ikea_product for detail or ikea_suggest for autocomplete.

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

Deploy Server

Other Tools