Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

BugSnag: Get Trace

bugsnag_get_trace
Read-onlyIdempotent

Retrieve all spans within a trace to debug slow requests and identify bottlenecks in distributed systems.

Instructions

Get all spans within a specific trace

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.

  • traceId (string) required: Trace ID

  • from (string) required: Start time (ISO 8601 format)

  • to (string) required: End time (ISO 8601 format)

  • targetSpanId (string): Optional target span ID to focus on

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

Use Cases: 1. Debug slow requests by viewing all operations in the trace 2. Understand the flow of a request through the system 3. Identify bottlenecks in distributed systems

Examples:

  1. Get all spans for a trace

{
  "traceId": "abc123",
  "from": "2024-01-01T00:00:00Z",
  "to": "2024-01-01T23:59:59Z"
}

Expected Output: Array of all spans in the trace with timing and hierarchy

  1. Get spans for a trace with pagination and target span

{
  "traceId": "def456",
  "from": "2024-01-01T00:00:00Z",
  "to": "2024-01-01T23:59:59Z",
  "targetSpanId": "span-789",
  "perPage": 50
}

Expected Output: Array of up to 50 spans focused around the target span

Hints: 1. Traces show the complete execution path of a request 2. Use from/to parameters to narrow the time window 3. targetSpanId can be used to focus on a specific span in the trace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesEnd time (ISO 8601 format)
fromYesStart time (ISO 8601 format)
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.
traceIdYesTrace ID
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.
targetSpanIdNoOptional target span ID to focus on
Install Server

TDQS

A4/5.0
Behavior5/5

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

Annotations already signal read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral detail beyond that: pagination via nextUrl with an explicit warning not to construct the URL manually, default page size, target-span focusing, and the return shape (array of spans with timing and hierarchy). This exceeds what the annotations alone provide.

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-structured with headings, use cases, examples, and hints, and the core action is front-loaded. However, it contains a full parameter list that duplicates the input schema and several hints that restate the examples, making it longer than necessary.

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 tool with no output schema, the description provides enough context: required parameters, optional pagination and target-span behavior, example invocations, and expected response shape. It could be more precise about the response structure, but an agent has the information needed to select and call the tool.

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 description coverage is 100%, so the schema already documents every parameter. The description repeats those definitions and adds illustrative examples, but it does not materially expand on the schema's parameter explanations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line 'Get all spans within a specific trace' names a specific verb and resource, so it is immediately clear what the tool returns. It does not explicitly distinguish itself from sibling BugSnag span tools such as bugsnag_list_spans, though 'specific trace' narrows the scope.

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 clear use cases (debugging slow requests, understanding request flow, identifying bottlenecks) and hints about narrowing the time window and focusing on a target span. It does not name sibling alternatives or state when not to use it, but the context is strong enough for an agent to decide.

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