Crawlora MCP

ikea_search

Read-only

Search IKEA products: normalized 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. A zero total with an empty products list is a valid no-results response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "ikea_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Required. Free-text product search query.
`size`	No	Optional. Result count, 1-100. Defaults to 24.
`country`	No	Optional. Lowercase 2-letter IKEA site country code. Defaults to us.
`language`	No	Optional. Lowercase 2-letter IKEA site language code. Defaults to en.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the normalized fields returned, that an IKEA item number resolves to its own single result, and that a zero total with an empty products list is a valid no-results response rather than an error.

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?

Three sentences, front-loaded with purpose before the edge cases, and every sentence carries information. Slight redundancy in enumerating return fields that an output schema already defines keeps it from a 5.

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?

An output schema exists, so return-value detail need not be re-explained. The description covers the required query, the item-number case, and no-results semantics, leaving little an agent needs to call it correctly.

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. The description earns an extra point by adding meaning the schema lacks: q not only takes free text but also accepts an IKEA item number, which resolves to a single result — a non-obvious semantic the schema's 'Free-text product search query' does not convey.

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?

States a specific verb (Search) and resource (IKEA products) plus the shape of the returned data, so an agent knows exactly what this tool produces. It does not explicitly differentiate itself from siblings like ikea_product (detail) or ikea_suggest (autocomplete), leaving that routing to inference.

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?

The description implies usage ('q is a free-text query') and notes a useful edge case (item numbers resolve as a single result), but never states when to prefer this over ikea_product or ikea_suggest. Usage context is implied rather than prescribed.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?