Skip to main content
Glama
Sign In
bol-mcp

bol-mcp

by BartWaardenburg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Product List

get_product_list
Read-only

Retrieve a product list from bol.com by category or search term, returning EAN and title for each item.

Instructions

Search or browse products on bol.com by category or search term. Returns a list of products with EAN and title.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryCodeNoCountry code.
categoryIdNoCategory ID to browse products in.
searchTermNoSearch term to find products.
pageNoPage number (default 1).
sortNoSort order for the product list.
filterRangesNoFilter ranges to apply.
filterValuesNoFilter values to apply.
languageNoLanguage for the response (Accept-Language header).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

The description adds value beyond annotations (readOnlyHint, openWorldHint) by specifying the output includes EAN and title. It does not contradict annotations. However, it could mention pagination or that either categoryId or searchTerm is needed.

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 sentences, front-loaded with purpose and action. No wasted words. Efficiently communicates core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate but could be more complete: no mention of pagination, required parameter combos, or result structure beyond EAN and title. With no output schema, the description should cover typical usage aspects.

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 baseline is 3. The description only adds meaning for category and search term ('by category or search term') but not for other parameters like filters, sort, or language.

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 clearly states it searches or browses products on bol.com by category or search term, and returns a list with EAN and title. This distinguishes it from sibling tools like get_catalog_product (single product) or get_product_list_filters (filters only).

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 use when needing a list of products, but lacks explicit guidance on when to prefer this over siblings like get_search_terms or get_product_placement. No when-not or alternative tools mentioned.

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