Jam
Capture and report bugs with automatic screen recordings and environment details.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- GetDetails: Retrieve comprehensive metadata and details for a specific Jam bug report. Returns essential information including: unique identifiers, author details, description, timestamps (created/upd
- GetNetworkRequests: Extract network activity logs captured during the Jam session. Returns HTTP/HTTPS requests including: URLs, methods (GET/POST/etc), status codes, headers, payloads, response times,
- GetConsoleLogs: Retrieve browser console output captured during the Jam session. Includes JavaScript errors, warnings, info messages, debug logs, and stack traces. Use logLevel filter to focus on spec
What data it sees
Do you need an account
No: the server works without sign-in
Capture and report bugs with automatic screen recordings and environment details. Create, view, and manage bug reports with full context.
Server tool list (15)
Raw names from tools/list. Only developers need these.
| getDetails | Retrieve comprehensive metadata and details for a specific Jam bug report. Returns essential information including: unique identifiers, author details, description, timestamps (created/updated), type (video/screenshot), and associated metadata. This is the primary entry point for analyzing any Jam - always call this tool first to understand the context before using other tools. |
| getNetworkRequests | Extract network activity logs captured during the Jam session. Returns HTTP/HTTPS requests including: URLs, methods (GET/POST/etc), status codes, headers, payloads, response times, and error details. Use filters to reduce output: statusCode (e.g., 500 or '5xx'), contentType (e.g., 'application/json'), host (e.g., 'api.example.com'), method (e.g., 'POST'), limit (max events). Essential for debugging API issues, failed requests, CORS problems, and performance bottlenecks. |
| getConsoleLogs | Retrieve browser console output captured during the Jam session. Includes JavaScript errors, warnings, info messages, debug logs, and stack traces. Use logLevel filter to focus on specific log levels (error, warn, info, log, debug). Critical for identifying runtime errors, debugging application state issues, and understanding the sequence of events leading to bugs. |
| getUserEvents | Access the complete timeline of user interactions captured in the Jam. Returns chronological sequence of: clicks, keyboard inputs, form submissions, navigation events, scroll actions, and other DOM interactions. Invaluable for reproducing bugs and understanding user behavior patterns that triggered issues. |
| getMetadata | Retrieve custom metadata set via the jam.metadata() SDK. Returns key-value pairs defined by the application developer, such as user IDs, app versions, feature flags, or any custom debugging context. |
| getScreenshots | Retrieve visual screenshots and image attachments from screenshot-type Jams. Returns image data that can be analyzed for UI issues, visual bugs, layout problems, or design inconsistencies. Note: This tool only works with Jams of type 'screenshot' - use getDetails first to verify Jam type. |
| analyzeVideo | Extract user intents from a Jam recording. Identifies distinct user goals, issues, and feedback with detailed context including visual observations, interactions, and technical indicators. |
| getVideoTranscript | Retrieve the speech transcript (captions) from a video Jam recording in WebVTT format with timestamps. Only available for video Jams where the microphone was enabled during recording. Use this to understand what the user said while recording the bug report. |
| fetch | Retrieve comprehensive metadata and details for a specific Jam bug report. Returns essential information including: unique identifiers, author details, description, timestamps (created/updated), type (video/screenshot), and associated metadata. This is the primary entry point for analyzing any Jam - always call this tool first to understand the context before using other tools. |
| search | Search for a Jam by extracting a UUID from a query string, jam.dev URL, or pasted text and returning matching Jam metadata. |
| listJams | List Jam bug reports with filtering and pagination. Search by text, filter by type (video/screenshot/replay), folder, author, URL, or creation date. Returns Jam metadata including title, author, folder, and timestamps. Use this to find specific Jams or browse the team's bug reports. |
| listFolders | List folders in the team with optional search and pagination. Returns folder metadata including name, short ID, Jam count, and timestamps. Use this to discover available folders for organizing Jams. |
| listMembers | List team members with optional search and pagination. Returns user metadata including name, email, and role. Use this to find users for filtering Jams by author. |
| createComment | Add a new comment to a Jam bug report. The comment body supports Markdown formatting. Use this to add notes, analysis results, or follow-up information to a Jam. |
| updateJam | Update a Jam bug report. Currently supports moving Jams between folders. Use folder name, folder ID, folder short ID, or "root" to move to the root level. |