Skip to main content
Glama

browser_get_attribute

Extract attribute values from web elements using locator strategies like ID, CSS, or XPath for automated web testing and data retrieval.

Instructions

Gets the value of an attribute from an element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byYesLocator strategy to find element
valueYesValue for the locator strategy
timeoutNoMaximum time to wait for element in milliseconds
attributeYesName of the attribute to get

Implementation Reference

  • Registers the browser_get_attribute tool with MCP server.tool(), including input schema (locatorSchema + attribute field) and the handler function that creates ElementService and calls getElementAttribute.
    server.tool(
      'browser_get_attribute',
      'Gets the value of an attribute from an element',
      {
        ...locatorSchema,
        attribute: z.string().describe('Name of the attribute to get'),
      },
      async ({ by, value, attribute, timeout = 15000 }) => {
        try {
          const driver = stateManager.getDriver();
          const elementService = new ElementService(driver);
          const attrValue = await elementService.getElementAttribute({
            by,
            value,
            attribute,
            timeout,
          });
          return {
            content: [
              {
                type: 'text',
                text: `Attribute "${attribute}" has value: ${attrValue}`,
              },
            ],
          };
        } catch (e) {
          return {
            content: [
              {
                type: 'text',
                text: `Error getting attribute: ${(e as Error).message}`,
              },
            ],
          };
        }
      }
    );
  • Core handler logic in ElementService class: locates the element using findElement and retrieves the specified attribute value using Selenium WebElement.getAttribute()
    async getElementAttribute(params: LocatorParams & { attribute: string }): Promise<string | null> {
      const element = await this.findElement(params);
      return element.getAttribute(params.attribute);
    }
  • Zod schema object for common locator parameters (by, value, timeout), spread into the tool's input schema.
    export const locatorSchema = {
      by: z
        .enum(['id', 'css', 'xpath', 'name', 'tag', 'class', 'link', 'partialLink'])
        .describe('Locator strategy to find element'),
      value: z.string().describe('Value for the locator strategy'),
      timeout: z.number().optional().describe('Maximum time to wait for element in milliseconds'),
    };
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 burden of behavioral disclosure. It states the action ('Gets') but lacks details on error handling (e.g., if the element or attribute doesn't exist), performance implications, or prerequisites like requiring an open browser. This leaves gaps in understanding how the tool behaves in practice.

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 a single, clear sentence with zero wasted words: 'Gets the value of an attribute from an element.' It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

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?

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action but lacks context on return values (e.g., string or null), error cases, or integration with sibling tools. While concise, it doesn't fully address the operational needs for a browser automation tool.

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?

The input schema has 100% description coverage, clearly documenting all four parameters (by, value, timeout, attribute) with enums for 'by'. The description doesn't add any semantic details beyond this, such as examples of attribute names or timeout defaults. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the tool's purpose: 'Gets the value of an attribute from an element.' It specifies the verb ('Gets') and resource ('attribute from an element'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like 'browser_get_element_text' or 'browser_get_cookie_by_name', which also retrieve values but from different sources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like retrieving specific HTML attributes (e.g., 'href', 'src') or compare it to siblings such as 'browser_get_element_text' for text content. Without such context, users must infer usage from the tool name alone.

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/pshivapr/selenium-mcp'

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