Retrieves a paginated list of all product IDs from Braze purchase events. Use it to audit which products are tracked in your customer engagement data.
List all product IDs from purchase events.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| apiKey | No | Braze REST API key | |
| restEndpoint | No | Braze REST endpoint URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation, but nothing is said about authentication (the apiKey param), pagination behavior, or whether results are scoped to a time range or workspace.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short, front-loaded sentence with no filler. Every word contributes to identifying the tool's output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and an undocumented page parameter, the definition is under-specified for a list endpoint. An agent lacks pagination, auth, and scoping details needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description says nothing about any of the three parameters. Schema coverage is only 67%: apiKey and restEndpoint are documented in the schema, but 'page' has no description anywhere, and the description does not compensate for that gap or explain pagination.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and a precise resource (product IDs from purchase events). This clearly separates it from sibling analytics tools like purchases_quantity and purchases_revenue, though it doesn't explicitly name those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus purchases_quantity, purchases_revenue, or events_list. No prerequisites, time-window constraints, or conditions for selection are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.