Skip to main content
Glama
Sign In

Traceo

by io.github.muhamad-0
OverviewDiscussionsAdmin

Get Traceo recording summary

get_recording
Read-onlyIdempotent

Start here. Summarizes a Traceo bug recording from its share link: page, environment (browser, viewport, locale), duration, event counts, the first errors and failed requests, the user actions leading up to the first error, and which tool to call next.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recording": "<recording>"
    },
    "name": "get_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordingYesTraceo share link (e.g. https://www.traceo.dev/abc123...) or recording id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is covered structurally. The description adds real value by disclosing the return contents (a summary with environment, counts, first errors), which matters because there is no output schema. It says nothing about failure behavior for an invalid or expired share link, or about data completeness/limits.

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?

Two sentences, with the imperative "Start here" front-loaded and the payload enumeration packed into a single readable list. Nothing is redundant with the title or the schema.

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 read-only summary tool with one parameter and no output schema, the description successfully carries the return-value burden by listing the summary's contents and the next-step routing. The only meaningful gap is undefined behavior for a malformed or inaccessible recording link.

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 single parameter is documented with an example link and the id alternative. The description repeats "from its share link" but adds no syntax, ID-format, or validation detail beyond what the schema already states, so the baseline of 3 applies.

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?

States a specific verb (summarizes) and resource (a Traceo bug recording), then enumerates exactly what the summary contains: page, environment, duration, event counts, first errors, failed requests, and preceding user actions. This granularity of content distinguishes it from granular siblings like get_console_logs, get_network_requests, or get_user_actions, which return one data type each.

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?

"Start here" gives explicit entry-point guidance, and "which tool to call next" signals it is a routing/orientation step before drilling into detail tools. It stops short of naming a when-not condition or a specific alternative, so it is strong context rather than full routing rules.

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

All Traceo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources