Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Element

get_element

Get exact position, size, state, and attributes of a single element using its element ID. Returns XML with full details.

Instructions

Get complete details for one element: exact position, size, state, and attributes. Requires an eid obtained from find or snapshot. Use when you need precise geometry or full attribute/state data for a single element. Returns the element details as XML.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eid": "<eid>"
    },
    "name": "get_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
eidYesElement ID to inspect, obtained from find results or the page snapshot.
page_idNoPage ID. If omitted, operates on the most recently used page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / eid / description
      Added value: +"Element ID to inspect, obtained from find results or the page snapshot."
    • addedInput schema / properties / page_id / description
      Added value: +"Page ID. If omitted, operates on the most recently used page."
  2. First observedv4.6.4

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states the tool returns element details as XML, implying a read-only operation. However, it does not disclose potential error conditions, performance, or other side effects, which is acceptable for a simple inspection tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (three clear statements: purpose, prerequisite, use case, return format) and front-loaded with the core action. No redundancy, but could be slightly more efficient.

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?

For a simple read tool without output schema, the description adequately covers prerequisites, purpose, and return format (XML). It does not detail the XML structure, but that is acceptable given the low complexity.

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 baseline is 3. The description adds context that eid comes from find/snapshot, but page_id's behavior is already described in schema. Minimal additional value.

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 retrieves complete details (position, size, state, attributes) for a single element, and distinguishes it from sibling tools like find or click by noting it requires an eid from find/snapshot and is for inspection.

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?

Explicitly says 'Use when you need precise geometry or full attribute/state data for a single element' and mentions the prerequisite (eid from find/snapshot). Does not explicitly list when not to use, but context from sibling tools implies alternatives.

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

Deploy Server

Other Tools