Skip to main content
Glama

page_elements

Lists visible interactive elements (links, buttons, inputs) with numbers so you can target them for clicking or typing.

Instructions

List visible interactive elements (links, buttons, inputs) with numbers. Use the numbers with click and type.

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": "page_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.
maxItemsNoDefault 200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that elements are visible, interactive, and numbered, but omits whether the operation is read-only, how numbering or ordering behaves, whether hidden elements are excluded, and any truncation behavior beyond the schema's maxItems.

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 two short sentences with no filler. The purpose is front-loaded, and the follow-up sentence efficiently explains how the numbered output should be used.

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?

For a simple listing tool with fully described parameters, the description covers the core purpose and numbered output handles. However, because there is no output schema and no annotations, it should do more to explain the returned structure and basic behavioral guarantees such as read-only nature and visibility scope.

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 schema already documents tabId and maxItems. The description does not add any additional meaning about these parameters, so the baseline score 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 and resource: 'List visible interactive elements (links, buttons, inputs) with numbers.' This clearly distinguishes the tool from page_text and screenshot by focusing on interactive elements rather than page text or images.

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 second sentence, 'Use the numbers with click and type,' gives downstream usage context, implying this tool should be called before interacting with elements. However, it does not explicitly say when to use this tool versus alternatives such as page_text, nor does it state exclusions.

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