Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ikea_product

Retrieve an IKEA product's full details by item number, including name, price, rating, images, quick facts, and category path.

Instructions

Get an IKEA product's detail. Returns one IKEA item's full detail: name, price, rating, every product image, quick facts, and category breadcrumb path. item_no is IKEA's own item number (8 digits, optionally prefixed with "s" for a combination/set article), taken from a search result's item_no field or an ikea.com product page's own URL.

Input Schema

NameRequiredDescriptionDefault
countryNoLowercase 2-letter IKEA site country code
item_noYesIKEA item number
languageNoLowercase 2-letter IKEA site language code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It thoroughly discloses what is returned (name, price, rating, all images, quick facts, breadcrumb path), which is valuable since there is no output schema. It omits error/pagination/marketplace-variation behavior, so not a 5.

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?

Three tight sentences, front-loaded with purpose then return contents then parameter format. No filler; each sentence carries distinct information.

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?

With no annotations and no output schema, the description adequately covers both purpose and return shape, plus item_no format and provenance. It stops short of noting country/language defaults or failure modes, minor gaps for a read-only detail lookup.

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%, establishing a baseline of 3, but the description adds real meaning beyond the schema: item_no's 8-digit format, the optional 's' prefix for combination/set articles, and the authoritative source of the value. country/language defaults are left unexplained.

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?

States a specific verb and resource ('Get an IKEA product's detail') and enumerates exactly what 'detail' includes (name, price, rating, images, quick facts, category breadcrumb). This clearly delineates it from siblings like ikea_search (which yields item_no) and ikea_availability/ikea_reviews.

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?

Provides clear context for use by telling the agent where item_no comes from ('a search result's item_no field or an ikea.com product page's own URL'), which implicitly routes the agent through ikea_search first. No explicit when-not-to-use or named alternative, so it falls short of a 5.

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