Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

BugSnag: List Releases

bugsnag_list_releases
Read-onlyIdempotent

List project releases filtered by release stage or visibility to correlate deployments with error spikes and paginate results.

Instructions

List releases for a project

Toolset: Releases

Parameters:

  • projectId (string): Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools.

  • releaseStage (string): Filter releases by this stage (e.g. production, staging), defaults to 'production' (default: "production")

  • visibleOnly (boolean): Whether to only include releases that are marked as visible in the dashboard (default: false)

  • perPage (number): How many results to return per page. (default: 30)

  • nextUrl (string): URL for retrieving the next page of results. Use the value in the previous response to get the next page when more results are available. Only values provided in the output from this tool can be used. Do not attempt to construct it manually.

Output Description: JSON array of release summary objects with metadata, with a URL to the next page if more results are available

Use Cases: 1. View recent releases to correlate with error spikes 2. Filter releases by stage (e.g. production, staging) for targeted analysis

Examples:

  1. List production releases for a project

{}

Expected Output: JSON array of release objects in the production stage

  1. List staging releases for a project

{
  "releaseStage": "staging"
}

Expected Output: JSON array of release objects in the staging stage

  1. Get the next page of results

{
  "nextUrl": "/projects/515fb9337c1074f6fd000003/releases?offset=30&per_page=30"
}

Expected Output: JSON array of release objects with metadata from the next page

Hints: 1. Use the Get Release tool to get more details on a specific release, including the builds it contains 2. The release stage defaults to 'production' if not specified 3. Use visibleOnly to filter out releases that have been marked as hidden in the dashboard

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextUrlNoURL for retrieving the next page of results. Use the value in the previous response to get the next page when more results are available. Only values provided in the output from this tool can be used. Do not attempt to construct it manually.
perPageNoHow many results to return per page.
projectIdNoUnique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools.
visibleOnlyNoWhether to only include releases that are marked as visible in the dashboard
releaseStageNoFilter releases by this stage (e.g. production, staging), defaults to 'production'production
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context beyond these: pagination semantics for nextUrl, default values for releaseStage and visibleOnly, the projectId side effect of setting the current project, and the output shape with next-page URL. All behavior is disclosed consistently.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with clear sections (Toolset, Parameters, Output, Use Cases, Examples, Hints). It is longer than necessary, but each section earns its place and the key information is front-loaded in the first sentence.

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?

For a read-only listing tool with five all-optional parameters, no output schema, and rich annotations, the description is fully sufficient. It documents every parameter, provides three worked examples, describes the output format, and gives hints for follow-up tools—nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description goes beyond the schema by providing concrete examples (staging filter, nextUrl usage) and restating defaults and constraints in context, which helps an agent apply parameters correctly without opening the schema.

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 action ('List releases for a project') with a specific verb and resource. The 'Toolset: Releases' label and the hint pointing to the 'Get Release tool' for more details help distinguish this listing tool from its sibling bugsnag_get_release.

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?

The description provides explicit use cases ('View recent releases to correlate with error spikes', 'Filter releases by stage') and a hint to use the Get Release tool when more detail on a specific release is needed. This gives clear when-to-use guidance and names an alternative.

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/SmartBear/smartbear-mcp'

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