aidemo

Overview Schema Source Related Servers Discussions Admin

inspect

Open a URL and list every visible interactive element with ranked unique selectors, headings, and iframes to choose accurate targets before writing automation. Poll the returned job ID for results.

Instructions

Open a URL in the recording profile (logged-in state included) and list every visible interactive element with UNIQUE selectors ranked data-testid → id → aria-label → role/text → name/placeholder → class → path, plus headings and iframes. Use it BEFORE writing targets — no selector guessing, no wasted probe. Writes logs/inspect-.json and a screenshot in the demo dir. Returns a jobId immediately — poll job_status. Rejects if another job is running.

Input Schema

TableJSON Schema

Name	Required	Description
`dir`	Yes	demo project directory — pass an absolute path
`url`	Yes	page to inspect (absolute URL)
`limit`	No	max elements (default 80)
`frames`	No	iframe selectors to scan too, as in the storyboard `frames` block
`profile`	No	Chrome user-data dir (default: the recording profile)
`headless`	No	default true
`useSetup`	No	honour the storyboard's setup block (storageState/cookies/preflight) so an authenticated page can be scanned. Default true.
`viewport`	No	default 1280x720 (use the storyboard's video size)
`storageState`	No	extra Playwright storageState JSON to seed before the scan

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`jobId`	Yes
`status`	Yes
`demoDir`	Yes	resolved absolute demo directory
`logFile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.15.1Sep 22, 2026

addedInput schema / properties / storageState

Added value: +{
+  "description": "extra Playwright storageState JSON to seed before the scan",
+  "type": "string"
+}

addedInput schema / properties / useSetup

Added value: +{
+  "description": "honour the storyboard's setup block (storageState/cookies/preflight) so an authenticated page can be scanned. Default true.",
+  "type": "boolean"
+}

Addedv0.14.1Sep 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden, and it does so thoroughly. It discloses side effects (writes logs/inspect-<n>.json and a screenshot), async behavior (returns a jobId, poll job_status), and a concurrency constraint (rejects if another job is running), plus that it uses the logged-in recording profile.

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?

The description is compact and front-loaded: main behavior first, then usage timing, then side effects and async/concurrency behavior. Every sentence contributes operational value, and there is no filler or repetition of schema content.

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 9 parameters, no annotations, and an output schema, the description covers the essential operational context: what it does, when to use it, what files it writes, how to get results, and a concurrency limitation. The output schema handles return-value details, so nothing critical is missing for correct invocation.

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 description coverage is 100%, so the baseline is 3; the description adds some contextual meaning around profile/authenticated state and job lifecycle but does not explain individual parameters beyond what the schema already provides. That is acceptable given the schema's coverage.

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 states a specific verb and resource: it opens a URL in the recording profile and lists every visible interactive element with ranked, unique selectors. This clearly distinguishes it from sibling tools like record, qa, or probe by positioning it as the selector-discovery step before writing targets, even though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It gives clear when-to-use guidance: 'Use it BEFORE writing targets — no selector guessing, no wasted probe.' This tells an agent the discovery phase it belongs to, but it does not explicitly state when not to use it or name alternative tools by comparison, so it falls just short of a 5.

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

Deploy Server