---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/b1a1d93e2d2d2623c85ef28d033e72f2/screenshot/63909e55-8aab-4ca2-90a5-c287a7bf4ace.png"
url: "https://jam.dev/c/fdc2175d-cabc-4a45-bbd9-63ccb4178947"
capturedOn: "https://dashboard.searchatlas.com/content/seo-content-assistant/b444e0ad-2975-4ae8-b697-647a771b7ec8"
type: "video"
browser: "Chrome 138.0.7204.185"
os: "Windows (x86) 11"
screen: "1920x869"
country: "CO"
timezone: "America/Bogota"
author: "Isabella Arango"
date: "2025-08-14T19:30:30.924Z"
---

## Signals

1 failed request · 2 interactions

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).
