Skip to main content
Glama

Get Collection Statistics

get_collection_stats

Get Bruno collection stats: counts by method, folder, environment, and per-request details. Filter to narrow scope or exclude requests for counts-only overview.

Instructions

Get statistics about a Bruno collection — request counts by method, folders, environments, and per-request details including each request's file path and URL. environmentDetails lists each environment with the NAMES of the variables it declares (values are withheld), so you can see what an environment already defines before merging into it with set_environment_variable. Use filePath values as entries in the requests list of run_collection.

SIZE: the per-request array is the bulk of the response and grows with the collection — a few hundred requests run to tens of kilobytes. Narrow it with folder, method or nameContains, or pass includeRequests: false for counts only. The counts always describe the WHOLE collection; a filtered call adds matchedRequests so the two cannot be confused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoReport only requests in this folder, path relative to the collection root. Nested folders are included, so "auth" also matches "auth/oauth2".
methodNoReport only requests with this method, case-insensitive. A request that has no method is bucketed under its kind, so "GRPC" and "WS" work here too.
nameContainsNoReport only requests whose name contains this text, case-insensitive.
collectionPathYesAbsolute path to collection directory. Use the path returned by list_collections.
includeRequestsNoSet false to drop the per-request array and return only the counts, folders and environments.
Install Server

TDQS

A4.8/5.0
Behavior4/5

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

The description explains the behavior thoroughly: it returns counts and details, mentions that environment variable values are withheld, and discusses response size and filtering side effects. Although no read-only annotation exists, the nature of 'Get statistics' implies no modifications, and the description makes the operational behavior clear.

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 well-structured in two logical paragraphs: first describing the output components, then addressing response size and filtering. It is concise, with no redundant phrasing, and every sentence adds valuable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity—multiple filtering options, response size considerations, and the relationship between counts and per-request data—the description covers all necessary aspects, including the use of filePath in run_collection, making it self-sufficient for an agent.

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?

All five parameters (collectionPath, folder, method, nameContains, includeRequests) are mentioned and explained in the description. It details the semantics of each, such as folder nesting, case-insensitivity, and the meaning of includeRequests, exceeding the bare schema documentation.

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 the tool's function: 'Get statistics about a Bruno collection' with specifics on counts by method, folders, environments, and per-request details. It distinguishes itself by providing filePath for use in run_collection, making its unique purpose evident.

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?

Explicit guidance on when to use the tool is provided: to obtain statistics and to use filePath values in run_collection. It also explains how to narrow results via folder, method, nameContains, and includeRequests, and clarifies the distinction between total counts and matchedRequests.

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

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/Ostico/bruno-mcp-studio'

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