Kitsune

Overview Schema Source Related Servers Discussions Admin

browser_snapshot

Read-only

Capture an accessibility snapshot of the current browser page to inspect element structure for automation or debugging, instead of relying on a visual screenshot.

Instructions

Capture accessibility snapshot of the current page, this is better than screenshot

Input Schema

Name	Required	Description
`boxes`	No	Include each element's bounding box as [box=x,y,width,height] in the snapshot. Coordinates are viewport-relative, in CSS pixels (Element.getBoundingClientRect)
`depth`	No	Limit the depth of the snapshot tree
`target`	No	Exact target element reference from the page snapshot, or a unique element selector
`filename`	No	Save snapshot to a file instead of returning it in the response. Relative file names are resolved against the workspace root.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.4.0Oct 24, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / boxes

Added value: +{
+  "description": "Include each element's bounding box as [box=x,y,width,height] in the snapshot. Coordinates are viewport-relative, in CSS pixels (Element.getBoundingClientRect)",
+  "type": "boolean"
+}

addedInput schema / properties / depth

Added value: +{
+  "description": "Limit the depth of the snapshot tree",
+  "type": "number"
+}

addedInput schema / properties / filename

Added value: +{
+  "description": "Save snapshot to a file instead of returning it in the response. Relative file names are resolved against the workspace root.",
+  "type": "string"
+}

removedInput schema / properties / max_depth

Removed value: -{
-  "description": "Depth (>= 0) below the subtree root (body by default); 0 is the root only, omitted all.",
-  "type": "integer"
-}

removedInput schema / properties / ref

Removed value: -{
-  "description": "Subtree root ref, resolved before refs are replaced; wins over selector.",
-  "type": "string"
-}

removedInput schema / properties / selector

Removed value: -{
-  "description": "CSS subtree root (included).",
-  "type": "string"
-}

removedInput schema / properties / tab_id

Removed value: -{
-  "description": "Default: active tab.",
-  "type": "integer"
-}

addedInput schema / properties / target

Added value: +{
+  "description": "Exact target element reference from the page snapshot, or a unique element selector",
+  "type": "string"
+}

removedInput schema / properties / text

Removed value: -{
-  "default": false,
-  "description": "Visible text lines (no refs), url, title and tabId, capped at 12,000 chars with a truncation marker.",
-  "type": "boolean"
-}

Changed22 schema fields changedv0.3.0Oct 22, 2026

removedInput schema / properties / max_depth / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / max_depth / default
```
Removed value: -null
```

addedInput schema / properties / max_depth / description

Added value: +"Depth (>= 0) below the subtree root (body by default); 0 is the root only, omitted all."

removedInput schema / properties / max_depth / title
```
Removed value: -"Max Depth"
```
addedInput schema / properties / max_depth / type
```
Added value: +"integer"
```

removedInput schema / properties / ref / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / ref / default
```
Removed value: -null
```

addedInput schema / properties / ref / description

Added value: +"Subtree root ref, resolved before refs are replaced; wins over selector."

removedInput schema / properties / ref / title
```
Removed value: -"Ref"
```
addedInput schema / properties / ref / type
```
Added value: +"string"
```

removedInput schema / properties / selector / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / selector / default
```
Removed value: -null
```
addedInput schema / properties / selector / description
```
Added value: +"CSS subtree root (included)."
```
removedInput schema / properties / selector / title
```
Removed value: -"Selector"
```
addedInput schema / properties / selector / type
```
Added value: +"string"
```

removedInput schema / properties / tab_id / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / tab_id / default
```
Removed value: -null
```
addedInput schema / properties / tab_id / description
```
Added value: +"Default: active tab."
```
removedInput schema / properties / tab_id / title
```
Removed value: -"Tab Id"
```
addedInput schema / properties / tab_id / type
```
Added value: +"integer"
```

addedInput schema / properties / text

Added value: +{
+  "default": false,
+  "description": "Visible text lines (no refs), url, title and tabId, capped at 12,000 chars with a truncation marker.",
+  "type": "boolean"
+}

removedInput schema / title

Removed value: -"browser_snapshotArguments"

AddedOct 19, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the result is an accessibility snapshot rather than a visual screenshot, which is useful behavioral context, but it does not describe the output structure or any other side effects. With annotations present, this is adequate but not rich.

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 a single efficient sentence that front-loads the action and object. The comparative note about screenshots earns its place by helping tool selection without adding bloat.

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

Completeness4/5

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

The tool is simple, read-only, and all parameters are documented in the schema. The description covers the core behavior and differentiates from screenshots, though it could be slightly more explicit about what the returned accessibility snapshot contains given there is no output schema.

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%, with all four parameters clearly documented in the input schema. The description itself adds no parameter-level meaning, so the baseline of 3 applies.

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 ('Capture') and resource ('accessibility snapshot of the current page'), making the tool's function immediately clear. It also distinguishes itself from the screenshot alternative, which is directly relevant to sibling browser_take_screenshot.

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?

The phrase 'this is better than screenshot' provides a clear comparison and implicit routing away from browser_take_screenshot. However, it does not explicitly state when not to use this tool or list other alternatives, so the guidance is context rather than a full routing rule.

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

browser_snapshot

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools