Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Probe Page

probe_page
Read-only

Probe one or more URLs to get their rendered state: screenshots, page metadata, console errors, and network summaries. Smoke-test routes after refactors or verify pages render correctly.

Instructions

Probe one or more URLs and return their rendered state — screenshot, page metadata (title/finalUrl/statusCode/loadTimeMs), structured console errors, and per-URL network summary (refetch loops collapse into one row by origin+pathname).

WHEN TO USE: "did I just break /settings?" / "smoke-test these 5 routes after my refactor" / "what's actually rendering at /dashboard?" — fast (<10s for 1 URL, <25s for 20), no LLM cost, no agent loop.

NOT FOR: scenario verification (sign in → click X → assert Y), interaction (clicks, form fills, scrolls), or anything requiring agent decisions. Use check_app_in_browser for those.

LOCALHOST SUPPORT: any localhost URL is auto-tunneled. Pre-flight TCP probe fails fast (<2s) if the dev server isn't listening.

BATCH MODE: pass up to 20 targets in one call to share browser session + tunnel — dramatically faster than firing parallel single-URL probes (one execution unit, not N). Per-URL waitForSelector / waitForLoadState / timeoutMs override defaults.

A single failed target's error appears in result.error without failing the whole batch — the other results stay valid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetsYes1-20 URLs to probe. Each entry can carry its own per-URL wait config.
includeHtmlNoIf true, each result includes the page's outerHTML. Default false to keep response size sane.
captureScreenshotsNoIf true (default), one PNG screenshot is returned per target. Set false for very large batches or when only the structured data matters.
repoNameNoGitHub repository name (e.g. 'my-org/my-repo'). Auto-detected from the current git repo — only provide this to scope the probe to a different project context.
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), describes batch behavior, error handling (single failure doesn't fail batch), localhost auto-tunnel, fast pre-flight TCP probe, and per-URL override defaults. No contradictions.

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?

Well-structured with clear sections (WHEN TO USE, NOT FOR, LOCALHOST SUPPORT, BATCH MODE). Every sentence earns its place; no fluff. Front-loaded with what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (4 params, no output schema), describes return values (screenshot, metadata, console errors, network summary), batch behavior, error handling, localhost support, timeouts. Sufficient for agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% so baseline 3. Description adds meaningful context: explains per-URL wait overrides, default values for includeHtml and captureScreenshots, auto-detection for repoName. Provides value beyond schema.

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?

Clearly states verb 'probe' and resource 'URLs', lists return data (screenshot, metadata, errors, network summary). Explicitly distinguishes from sibling 'check_app_in_browser' by stating what it is NOT for and recommending the sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete WHEN TO USE examples ('did I just break /settings?', 'smoke-test these 5 routes') and explicitly excludes scenario verification, interaction. References sibling tool and batch mode best practices.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/debugg-ai/debugg-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server