Crawlora MCP

ikea_category

Read-only

One page of an IKEA category's product listing, with real offset/size pagination and sort. category is IKEA's own category key (e.g. 20649), taken from a category URL's trailing -{key}/ segment or a product's own category_path field.

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": {
      "category": "<category>"
    },
    "name": "ikea_category"
  }
}

Input Schema

Name	Required	Description
`size`	No	Optional. Result count, 1-100. Defaults to 24.
`sort`	No	Optional. One of relevance, price-low, price-high, newest, rating, name, popular, width, height, depth, length. Defaults to relevance.
`offset`	No	Optional. Zero-based result offset. Defaults to 0.
`country`	No	Optional. Lowercase 2-letter IKEA site country code. Defaults to us.
`category`	Yes	Required. IKEA category key, e.g. 20649.
`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.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that pagination and sort are 'real' (server-side), which is mildly useful behavioral context, but says nothing about rate limits, result caps, or return shape. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two tight sentences with no filler. The core behavior is front-loaded and the key-sourcing detail follows immediately, so every clause earns its place.

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 values needn't be explained, and 5 of 6 parameters are fully documented in the schema. The description covers the one genuinely non-obvious requirement (where the category key comes from). Missing only explicit sibling routing, which keeps it from a 5.

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% and the schema already documents size, sort, offset, country, and language with defaults, so the baseline is 3. The description adds real value on the sole required parameter by explaining the format and provenance of the category key (URL -{key}/ segment or category_path), information absent from the schema.

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 and resource: it returns 'one page of an IKEA category's product listing' with pagination and sort, which is clear and concrete. However it never names or contrasts with siblings like ikea_categories or ikea_search, so an agent must still infer which tool to reach for.

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?

There is no explicit when-to-use-this-vs-alternatives statement, but the description does tell the agent where to obtain the required category key (a category URL's trailing -{key}/ segment or a product's category_path field), which is genuine usage guidance. Routing between ikea_category, ikea_search, and ikea_categories is left implicit.

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?