webhallen-mcp

Get product reviews

get_reviews

Retrieve customer reviews for a Webhallen product by product ID or URL, newest first and paginated, to evaluate variant feedback before buying.

Instructions

Customer reviews for a product (mostly in Swedish), newest first, 15 per page. Reviews are shared across variants of the same product; productId says which variant a review was for.

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": {
      "idOrUrl": "<idOrUrl>"
    },
    "name": "get_reviews"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`idOrUrl`	Yes	Webhallen product id or URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does add genuine behavioral detail: newest-first ordering, fixed page size of 15, and mostly-Swedish content. However, it says nothing about what a returned review contains, what the total count is, or how to know when pages run out, which matters since there is no output schema.

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, front-loaded with the resource and the highest-value behavior (ordering and page size). Every clause carries information an agent would not get from the schema alone.

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 simple two-parameter read tool with no output schema, the description covers ordering, pagination size, language, and the variant-sharing caveat well. The main remaining gap is the shape of a returned review and how pagination terminates, which the absent output schema leaves undocumented.

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 coverage is 50%: idOrUrl is documented in the schema, but page is not, and the description only indirectly compensates by mentioning 15 per page and newest-first ordering. It also refers to a 'productId' value that is not an input parameter, which slightly muddies rather than clarifies how the input maps to results.

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 names a concrete resource (customer reviews for a product) and its scope, which is clearly distinct from siblings like get_product or check_price_availability. The retrieval verb is only implied by the noun phrase, but an agent can still identify the tool's job immediately.

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 rather than stated: the agent can infer this is the tool for reading reviews as opposed to getting product details. There is no explicit 'use this when' clause, no mention of prerequisites, and no routing advice toward or away from any sibling tool.

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

Deploy Server