Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Trigger App Crawl

trigger_crawl

Systematically explore web app pages, UI states, and navigation flows to build a project knowledge graph. Supports localhost URLs via automatic tunnel. Returns crawl execution status.

Instructions

Trigger a browser-agent crawl of a web app to build the project's knowledge graph. The crawl systematically explores pages, UI states, and navigation flows, then populates the backend's knowledge graph so future evaluations and tests have context about the app.

LOCALHOST SUPPORT: Pass any localhost URL (e.g. http://localhost:3000) and it Just Works. A secure tunnel is automatically created so the remote browser can reach your local dev server.

WHEN TO USE: after a significant new feature, a new environment, or when onboarding a project. NOT for per-change verification — use check_app_in_browser for that.

SCOPE: one crawl per call against one URL. The crawl is long-running (minutes to tens of minutes depending on app size) and populates backend state asynchronously; the tool returns the execution status once the workflow completes. This does NOT return pass/fail — it returns executionId + status + outcome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to crawl. Can be any public URL or a localhost/local dev server URL. For localhost URLs, a secure tunnel is automatically created — just make sure your dev server is running on that port.
projectUuidNoUUID of the project whose knowledge graph the crawl should populate. Auto-detected from the current git repo if omitted.
environmentIdNoUUID of a specific environment to use for the crawl. See available environments in the tool description above.
credentialIdNoUUID of a specific credential for authenticated crawls. See available credentials in the tool description above.
credentialRoleNoPick a credential by role (e.g. 'admin', 'guest') from the resolved environment.
usernameNoA real, existing account email for the target app. Do NOT invent credentials — use one from the available credentials or ask the user.
passwordNoThe real password for the username above. Do NOT guess.
headlessNoRun the browser in headless mode. Defaults to backend configuration.
timeoutSecondsNoMaximum wall-time the crawl may run, in seconds (1..1800). Backend enforces this per workflow execution.
repoNameNoGitHub repository name (e.g. 'my-org/my-repo'). Auto-detected from the current git repo — only provide this to run against a different project.
Behavior4/5

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

With no annotations, description discloses long-running nature, async state population, and return format (executionId+status+outcome). Also mentions localhost support. Lacks explicit mention of side effects beyond knowledge graph update.

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 sections (LOCALHOST SUPPORT, WHEN TO USE, SCOPE) and no unnecessary words. Efficiently conveys all key information.

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 10 parameters, long-running async behavior, and no output schema, the description covers purpose, usage, constraints, return value, and parameter context comprehensively.

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

Parameters3/5

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

Schema has 100% coverage with detailed descriptions. Description adds context for credentials and localhost but mostly restates schema. Baseline 3 is appropriate.

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?

The description clearly states the tool triggers a browser-agent crawl to build a knowledge graph, and explicitly distinguishes from sibling tool check_app_in_browser by indicating it's not for per-change verification.

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?

Explicitly specifies when to use (after significant feature, new environment, onboarding) and when not to use, with clear alternative named (check_app_in_browser).

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