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.