Skip to main content
Glama

Get Promotion Products

get_promotion_products
Read-only

Retrieve products participating in a specific promotion by providing the promotion ID. Optionally specify a page number for paginated results.

Instructions

Get the list of products participating in a specific promotion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promotionIdYesThe bol.com promotion ID.
pageNoPage number (1-based).
Behavior2/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description merely restates the obvious without adding any behavioral details (e.g., pagination handling, rate limits, or result completeness).

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?

Single, well-structured sentence that immediately conveys the tool's purpose. No extraneous information.

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?

Lacks details on return value fields and pagination behavior, which is relevant given the openWorldHint annotation and the page parameter. Adequate for a simple list but could be more informative.

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?

Input schema covers all parameters with descriptions, achieving 100% coverage. Description adds no extra meaning beyond the schema's parameter definitions.

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?

Description clearly states action ('Get'), resource ('list of products'), and scope ('participating in a specific promotion'), distinguishing it from siblings like list_promotions and get_promotion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., list_promotions or get_promotion). The description does not mention any prerequisites or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BartWaardenburg/bol-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server