Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

get_accessibility_tree

Retrieve a browser page's full accessibility tree so AI agents can understand page structure and locate interactive elements.

Instructions

Get the full accessibility tree of the page (ideal for AI understanding of page structure)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_accessibility_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a safe read via "Get", but says nothing about the default target when tabId is omitted, the expected output size/verbosity of a "full" tree, or whether results are truncated – all material for a no-annotation tool.

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?

One sentence, resource front-loaded, with the purpose hint in a short parenthetical. Nothing is wasted and no clause needs to be re-read.

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

Completeness3/5

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

With no output schema and no annotations, the description should say more about the return shape (how verbose a "full" tree is) and the default tab behavior. It is adequate to identify the tool but leaves gaps an agent would want closed before invoking it.

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% and the single optional param already documents "Tab ID (optional)". The description adds no meaning beyond that, so the neutral baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get the full accessibility tree of the page" names a specific verb and resource, so the agent knows exactly what it retrieves. The parenthetical distinguishes it in spirit from siblings like get_page_content or take_snapshot, but it never names those alternatives, so the differentiation is only implied.

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

Usage Guidelines3/5

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

The phrase "ideal for AI understanding of page structure" hints at when to reach for this tool, but there is no explicit when-to-use/when-not statement and no named alternative (e.g. get_page_content vs take_snapshot). An agent must infer the choice from the parenthetical alone.

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