Skip to main content
Glama

Find page elements

get_elements
Read-only

Get information about elements matching a selector

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": {
      "sessionId": "<sessionId>",
      "selector": "<selector>"
    },
    "name": "get_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector of the elements
sessionIdYesSession ID of the connected browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / selector / description
      Previous value: -"Selector CSS de los elementos"New value: +"CSS selector of the elements"
    • changedInput schema / properties / sessionId / description
      Previous value: -"ID de sesión del navegador conectado"New value: +"Session ID of the connected browser"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it does not say what 'information' is returned (attributes, text, position), whether all matches or only the first are reported, or how invalid or non-matching selectors behave.

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?

A single front-loaded sentence with no filler or redundancy, which is efficient. The terseness comes at the cost of substance rather than being a structural flaw, so it scores well on form.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining the return value, yet it only says 'information'. For a DOM-query tool whose result shape (list of matches, their attributes, text, bounding box) strongly affects downstream usage, this leaves a meaningful gap.

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 both sessionId and selector are already documented as CSS selector and browser session ID. The phrase 'matching a selector' restates the schema rather than adding format or constraint details, so the 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?

The description names a specific verb ('Get information') and a specific resource scoped by a CSS selector, so an agent knows it is an element lookup rather than a page-level fetch. It does not, however, differentiate itself from siblings such as get_page_content or take_screenshot, which also read the current page.

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

Usage Guidelines2/5

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

There is no guidance on when this tool should be chosen over get_page_content or the other browser-reading siblings, and no stated preconditions (e.g. that a connected session is required). The agent must infer usage entirely from the tool name and required parameters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources