Skip to main content
Glama

inspect_element

Determine an element's actual rendered state—box model, computed styles, visibility verdict—to see the values the page truly uses, bypassing overridden rules.

Instructions

The 'WHAT' for one element: box model (margins/padding/border), key computed styles as authored → used values, a visibility verdict, and layout context. Use when you need an element's current rendered state — its real size, spacing, or whether it is actually visible/where it sits. These are the values the page ACTUALLY renders, so it catches the common case where the source rule you'd edit is overridden or never applied. For 'WHY it looks like this / which rule wins' use explain_styles; for 'which ancestor constrains its size or position' use inspect_ancestors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoViewport x coordinate (use with y)
yNoViewport y coordinate (use with x)
uidNoElement uid from a prior page_snapshot (e.g. "e8")
verboseNoInclude all whitelisted computed properties, not just non-default ones
selectorNoCSS selector — first match is used
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses tool returns rendered values (not authored), catches overridden styles, and provides specific data categories. Lacks details on error handling or output format, but adequate for a read-only 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.

Conciseness5/5

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

Front-loaded with purpose, concise sentences, no wasted words. Parenthetical clarifications are 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?

Given 5 parameters, no output schema, and no annotations, description provides good context: explains when to use and what data is returned. Lacks explicit output format details but sufficient for agent to understand tool's role.

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 coverage is 100%, so baseline is 3. Description does not add parameter-specific details beyond schema; no extra meaning for parameters like x, y, uid, verbose, or selector.

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 returns the box model, computed styles, visibility verdict, and layout context for one element, using specific verbs and distinguishing from sibling tools like 'explain_styles' and 'inspect_ancestors'.

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 states when to use (need current rendered state) and when not to (use explain_styles for 'why it looks like this', inspect_ancestors for ancestor constraints), plus highlights benefit of catching overridden styles.

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/mi60dev/visionaire-engine'

If you have feedback or need assistance with the MCP directory API, please join our Discord server