Skip to main content
Glama
BigRedCloud

Red MCP Server

Official
by BigRedCloud

brc_batch_products

Process a batch of up to 5 products after previewing changes and obtaining explicit user confirmation. First call shows draft, second call posts.

Instructions

Processes a batch of products. Maximum 5 items per batch request. First call without confirmWrite: true returns confirmation_required and a payload preview — show a plain-English draft in chat, then retry with confirmWrite: true only after explicit user confirmation in a later message. Passing preflight is not confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesBatch items to process. Maximum 5 items per request.
priceBasisNoApplies to every sales invoice/credit note item in this batch. Required when Gross Price Entry is enabled. Use `gross` when unit prices are VAT-inclusive/gross. Use `net` when unit prices are VAT-exclusive/net.
companyNameYesCompany context name, for example YOUR-COMPANY-NAME.
confirmWriteNoMust be true only after a plain-English draft has been shown in the current conversation and the user explicitly confirmed posting (for example yes, create it / post it now / confirm). Never set true on the first call or because the user initially asked to create something.
confirmCrAnalysisCategoryNoApplies to every sales document item in this batch. Set true only after the user confirms a CR (customer) sales analysis account code is intentional for these product lines.
Behavior4/5

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

No annotations provided, but the description discloses the two-step confirmation workflow, including the return of a 'confirmation_required' response and a payload preview. It also clarifies that passing preflight is not confirmation. However, it does not detail error conditions or side effects beyond the confirmation flow.

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?

The description is concise (three sentences) and front-loaded with the core purpose. Every sentence provides essential information without redundancy.

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?

The description covers the confirmation workflow and key parameters. However, it lacks details about the output of the second call (e.g., success response or errors). Given no output schema, this would be helpful for the agent to understand the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all parameters. The description adds significant context beyond the schema: it explains the confirmWrite parameter's required usage pattern, the confirmCrAnalysisCategory parameter's purpose for CR analysis account confirmation, and the priceBasis parameter's condition and meaning (net vs gross).

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 'Processes a batch of products' and specifies the maximum batch size (5 items). It distinguishes itself from sibling tools like brc_create_product by handling batches and requiring a confirmation step.

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

Usage Guidelines5/5

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

Explicitly instructs the agent to first call without confirmWrite to get a preview, then retry with confirmWrite: true only after explicit user confirmation. Warns against setting confirmWrite on the first call or assuming preflight is confirmation.

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/BigRedCloud/red-mcp-server'

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