Deletes multiple items from a Braze catalog in one request, removing up to 50 entries by ID to keep catalog data accurate and current.
Delete multiple items from a catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Items to delete (max 50) | |
| apiKey | No | Braze REST API key | |
| catalog_name | Yes | Catalog name | |
| 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 behavioral burden, yet it says nothing about irreversibility, whether deletion is permanent, failure behavior for partial batches, or auth requirements. For a destructive batch operation this is a significant gap.
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 front-loaded sentence with zero filler. Nothing is repeated and the scope qualifier ('multiple') comes before the resource.
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 a destructive batch semantic, the description should disclose irreversibility and batch-failure behavior. Parameter documentation is fully handled by the schema, but the behavioral side is left entirely unaddressed.
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?
Schema description coverage is 100%, so all four parameters including the items array and its max-50 constraint are already documented. The description adds no format or syntax detail beyond the schema, making the baseline 3 appropriate.
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 (Delete) plus resource (items in a catalog) and scope (multiple). An agent can distinguish it from the singular catalog_item_delete and catalogs_delete without opening schemas, though it never names those siblings explicitly.
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?
No guidance on when to use this batch delete versus catalog_item_delete, nor any prerequisites such as API key scope or endpoint selection. The only usage constraint (max 50 items) lives in the schema, not the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.