PyScrappy

Overview Schema Source Related Servers Discussions Admin

Search Ikea

search_ikea

Search IKEA's online catalog for furniture and home products, returning product name, type, price, and rating from the selected country's live store listings.

Instructions

Search IKEA's online catalog for furniture and home products, returning a list of product dicts with fields name, type, price, and rating.

Scrapes the IKEA store website for the given country at call time, so results require network access and reflect that store's live listings. Prices, availability, and currency are per-country and per-language. Returns an empty list if the query matches no products.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	String language code for that store's listings; must be a language the chosen country's store supports, e.g. "en" for "us"/"gb" or "de" for "de". Example "de". Default "en".	en
`query`	Yes	String search term for the product name or type, e.g. "desk" or "bookshelf". Required, no default.
`country`	No	String two-letter IKEA store country code that sets pricing and availability; allowed values are IKEA market codes such as "us", "gb", "de", "fr", "se". Example "gb". Default "us".	us
`max_results`	No	Integer cap on the number of products returned; e.g. 10. Default 24.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 31, 2026

changedInput schema / properties / country / description

Previous value: -"IKEA store country code, e.g. \"us\", \"gb\", \"de\" (default \"us\")."New value: +"String two-letter IKEA store country code that sets pricing and availability; allowed values are IKEA market codes such as \"us\", \"gb\", \"de\", \"fr\", \"se\". Example \"gb\". Default \"us\"."

changedInput schema / properties / lang / description

Previous value: -"Language code for that store, e.g. \"en\", \"de\" (default \"en\")."New value: +"String language code for that store's listings; must be a language the chosen country's store supports, e.g. \"en\" for \"us\"/\"gb\" or \"de\" for \"de\". Example \"de\". Default \"en\"."

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of products to return (default 24)."New value: +"Integer cap on the number of products returned; e.g. 10. Default 24."

changedInput schema / properties / query / description

Previous value: -"Product search query, e.g. \"desk\" or \"bookshelf\"."New value: +"String search term for the product name or type, e.g. \"desk\" or \"bookshelf\". Required, no default."

Changed22 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / country / description

Added value: +"IKEA store country code, e.g. \"us\", \"gb\", \"de\" (default \"us\")."

removedInput schema / properties / country / title
```
Removed value: -"Country"
```

addedInput schema / properties / lang / description

Added value: +"Language code for that store, e.g. \"en\", \"de\" (default \"en\")."

removedInput schema / properties / lang / title
```
Removed value: -"Lang"
```

addedInput schema / properties / max_results / description

Added value: +"Maximum number of products to return (default 24)."

removedInput schema / properties / max_results / title
```
Removed value: -"Max Results"
```

addedInput schema / properties / query / description

Added value: +"Product search query, e.g. \"desk\" or \"bookshelf\"."

removedInput schema / properties / query / title
```
Removed value: -"Query"
```
removedInput schema / title
```
Removed value: -"search_ikeaArguments"
```

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

Addedv1.2.0Jul 26, 2026
Removedv1.2.0Jul 26, 2026
AddedJul 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does it well: it discloses live scraping at call time, network dependency, per-country/per-language pricing and availability, and the empty-list behavior for no matches. This goes well beyond what the input schema or tool name convey.

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?

The description is three concise sentences: purpose and return shape, live-scraping behavior with country/language context, and empty-result behavior. Every sentence adds distinct value, and the most important identifying information is front-loaded.

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 4-parameter tool with no annotations, the description covers the key operational caveats: live network scraping, per-country pricing, and empty results. An output schema exists and the return fields are named, so return-value details are adequately covered. Minor gaps remain around failure modes (e.g., network errors or blocked scraping), preventing a perfect score.

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 query, country, lang, and max_results in detail. The description adds useful context about country-specific live pricing, but it does not need to repeat parameter-level details; baseline 3 is appropriate.

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 IKEA's online catalog for furniture and home products.' It also names the return shape (list of product dicts with fields), which clearly distinguishes it from sibling tools like search_amazon or scrape_url.

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?

The description clearly establishes when this tool is appropriate: for IKEA-specific product searches with live store data. It does not explicitly name alternatives or exclusion conditions, but the context is clear enough that an agent can route to it versus the other catalog and search tools.

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