Execute Bruno API test collections via CLI to automate testing workflows, optionally using environment files and variables.
Run a Bruno Collection using Bruno CLI
| Name | Required | Description | Default |
|---|---|---|---|
| collection | Yes | Path to the Bruno collection | |
| environment | No | Optional path to environment file | |
| variables | No | Optional environment variables |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Run' which implies execution, but fails to describe critical behaviors like whether it's read-only/destructive, requires specific permissions, has side effects (e.g., file changes), or handles errors. This leaves significant gaps for an execution tool.
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?
The description is a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, clearly stating the core action without unnecessary elaboration.
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?
Given the complexity of running a collection (an execution tool with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, output format, error handling, or dependencies, making it inadequate for safe and effective use by an AI agent.
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 schema description coverage is 100%, so the schema already documents all parameters (collection path, optional environment file, optional variables). The description adds no additional meaning beyond what the schema provides, such as format examples or usage context, meeting the baseline for high coverage.
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?
The description clearly states the verb ('Run') and resource ('a Bruno Collection using Bruno CLI'), making the purpose understandable. However, it doesn't differentiate from siblings since there are none, so it can't achieve the full 5 points for sibling differentiation.
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?
The description provides no guidance on when to use this tool, such as prerequisites (e.g., Bruno CLI installation), alternatives, or specific contexts. It only states what the tool does without usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.