Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

BugSnag: List Span Groups

bugsnag_list_span_groups
Read-onlyIdempotent

List span groups to identify slow operations, sort by duration metrics, and filter by category or starred items for performance monitoring.

Instructions

List span groups (operations) tracked for performance monitoring

Toolset: Performance

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.

  • sort (enum): Field to sort by

  • direction (enum): Sort direction for ordering results (default: "desc")

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

  • starredOnly (boolean): Show only starred span groups

  • 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.

  • filters (record<string, array>): Apply filters to narrow down the span group list. Use the List Trace Fields tool to discover available filter fields. Time filters support extended ISO 8601 format (e.g. 2018-05-20T00:00:00Z) or relative format (e.g. 7d, 24h). (default: {"span.since":[{"type":"eq","value":"7d"}]})

Use Cases: 1. View all operations being tracked for performance 2. Find slow operations by sorting by duration metrics 3. Filter to starred/important span groups

Examples:

  1. List slowest operations

{
  "sort": "duration_p95",
  "direction": "desc",
  "perPage": 10
}

Expected Output: Array of span groups sorted by 95th percentile duration

  1. List starred span groups with filtering

{
  "starredOnly": true,
  "filters": {
    "span_group.category": [
      {
        "type": "eq",
        "value": "full_page_load"
      }
    ]
  }
}

Expected Output: Array of starred span groups filtered by category

Hints: 1. Span groups represent different operation types (page loads, API calls, etc.) 2. Use sort by duration_p95 or duration_p99 to find the slowest operations 3. Star important span groups for quick access 4. Use nextUrl for pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoField to sort by
filtersNoApply filters to narrow down the span group list. Use the List Trace Fields tool to discover available filter fields. Time filters support extended ISO 8601 format (e.g. 2018-05-20T00:00:00Z) or relative format (e.g. 7d, 24h).
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.
directionNoSort direction for ordering resultsdesc
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.
starredOnlyNoShow only starred span groups
Install Server

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description mainly adds value with behavioral caveats: the default span.since=7d filter, the nextUrl restriction that only prior output values are valid and must not be hand-constructed, and the projectId side effect of setting the current BugSnag project. These go beyond the structured annotations.

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

Conciseness3/5

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

The description is well organized with headings, a front-loaded purpose, use cases, examples, and hints, making it easy to scan. However, the Parameters section duplicates the schema verbatim, adding length without new information; the same content could be tighter.

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?

For a list tool with no output schema, the description covers invocation-relevant context well: defaults, pagination through nextUrl, filter format, example payloads, and expected array output. It does not enumerate response fields, but it provides enough for an agent to call the tool correctly.

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

Parameters3/5

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

Schema coverage is 100%, and the description largely restates the schema's parameter descriptions for sort, direction, perPage, filters, and nextUrl rather than adding new semantic detail. It does add working examples and sorting hints, which are useful, but they are supplements rather than necessary compensation for missing schema coverage.

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 opens with a specific verb and resource: 'List span groups (operations) tracked for performance monitoring'. This clearly identifies the tool as a list operation over span groups and distinguishes it from sibling tools like bugsnag_get_span_group or bugsnag_list_spans.

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

Usage Guidelines4/5

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

The Use Cases enumerate concrete scenarios: viewing all operations, finding slow operations via duration sorts, and filtering starred groups. Hints recommend duration_p95/duration_p99 for slowest operations, and the description points to List Trace Fields as the place to discover filter fields. It does not explicitly contrast with bugsnag_list_spans or bugsnag_get_span_group, so it stops short of a 5.

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