Jam

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.

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.

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.

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.

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.

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.

Extract still frames (thumbnails) from a video Jam recording as images, so you can see what was on screen. Use exactly one mode. Set `overview: true` to get one overview grid: N frames evenly spaced across the whole video (N scales with duration), stitched into a single image with each cell labeled by timestamp — the fastest way to orient on a visual jam. Or specify `at` (a list of timestamps in milliseconds) or a window (`fromMs`, `toMs`, `count`) to sample evenly-spaced frames across a range; each is returned as an image preceded by a `t=<ms>` text anchor. Use `size` to trade detail for context budget (small=360p, medium=720p, large=1080p; not applied to the overview grid). Only works for video Jams whose recording is available on Cloudflare Stream; ineligible Jams return a single text block explaining why. Frames per call are capped at 30.

Extract user intents from a Jam recording. Identifies distinct user goals, issues, and feedback with detailed context including visual observations, interactions, and technical indicators.

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.

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 for a Jam by extracting a UUID from a query string, jam.dev URL, or pasted text and returning matching Jam metadata.

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.