Skip to main content
Glama

get_element_text

Extract text content from a web element using a CSS selector with the MCP Browser Server, enabling automated data retrieval from web pages.

Instructions

Get text content of an element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the element
timeoutNoTimeout in milliseconds

Implementation Reference

  • Handler for 'get_element_text' tool: checks for current page, parses input parameters using GetElementTextSchema, retrieves the text content of the specified element using Playwright's page.textContent method with timeout, and returns the extracted text.
    case 'get_element_text': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = GetElementTextSchema.parse(args);
      const text = await currentPage.textContent(params.selector, { timeout: params.timeout });
    
      return {
        content: [
          {
            type: 'text',
            text: `Element text: ${text || '(empty)'}`
          }
        ]
      };
    }
  • Zod schema defining the input parameters for the 'get_element_text' tool: CSS selector (required) and optional timeout (default 5000ms).
    const GetElementTextSchema = z.object({
      selector: z.string(),
      timeout: z.number().default(5000)
    });
  • src/index.ts:237-255 (registration)
    Tool registration in the ListToolsRequestSchema handler, providing name, description, and JSON schema matching the Zod schema for client-side validation.
    {
      name: 'get_element_text',
      description: 'Get text content of an element',
      inputSchema: {
        type: 'object',
        properties: {
          selector: {
            type: 'string',
            description: 'CSS selector for the element'
          },
          timeout: {
            type: 'number',
            default: 5000,
            description: 'Timeout in milliseconds'
          }
        },
        required: ['selector']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It lacks details such as error handling (e.g., what happens if the element isn't found), performance implications, or whether it interacts with dynamic content, which are crucial for safe and effective use.

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, direct sentence with no wasted words, making it highly concise and front-loaded. Every word contributes to understanding the tool's purpose without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool with parameters and potential behavioral complexity. It doesn't explain return values, error cases, or interactions with dynamic web content, leaving significant gaps for the agent to infer.

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 both parameters. The description adds no additional meaning beyond what the schema provides, such as examples of CSS selectors or timeout behavior, so it meets the baseline for adequate but unenhanced parameter information.

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 verb ('Get') and resource ('text content of an element'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_page_info' or 'evaluate_javascript' that might also retrieve text, which prevents a perfect score.

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. For example, it doesn't specify if this is for extracting visible text from web elements or compare it to tools like 'evaluate_javascript' for more complex text retrieval, leaving the agent without contextual usage instructions.

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

Related 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/Wladastic/mcp-browser-server'

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