Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

BugSnag: List Span Groups

bugsnag_list_span_groups
Read-onlyIdempotent

List and filter span groups for performance monitoring. Sort by duration metrics to find slow operations, or filter by starred groups for quick access.

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
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavior beyond annotations: default values (sort direction 'desc', perPage 30, filters default 7d), pagination via nextUrl, and filter time format. It does not contradict annotations. Minor omission: no explicit statement of return format (though examples imply array).

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-structured with sections (Toolset, Parameters, Use Cases, Examples, Hints). It is front-loaded with purpose. While it repeats some parameter descriptions from the schema, it adds value with context and examples. No unnecessary sentences.

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?

Given the tool complexity (7 params, nested filters, pagination), the description covers purpose, filtering, sorting, pagination, and provides use cases and examples. It references a related tool for filter fields. Missing explicit output format details, but examples illustrate it. Overall, sufficient for an agent.

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 coverage is 100% (all parameters described in schema). The description adds context: for filters, it explains time format and suggests using List Trace Fields; for nextUrl, it warns against manual construction; for sort, it hints at useful values like duration_p95. This extra guidance exceeds the baseline of 3.

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 states 'List span groups (operations) tracked for performance monitoring' with a clear verb ('list') and resource ('span groups'). It distinguishes itself from sibling tools like bugsnag_get_span_group (fetches a single span group) and bugsnag_list_spans (lists individual spans). The title reinforces the purpose.

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 description provides explicit use cases (view all operations, find slow operations, filter starred groups) and two detailed examples. It suggests using the List Trace Fields tool for filter fields and hints for sorting and pagination. However, it does not explicitly state when not to use this tool or compare with siblings like bugsnag_get_span_group.

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

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