Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

get_element_text

Extract text content from a web element using a CSS selector with a customizable timeout via AutoProbeMCP's browser automation capabilities.

Instructions

Get text content of an element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the element
timeoutNoTimeout in milliseconds

Implementation Reference

  • Handler for the 'get_element_text' tool. Validates input with GetElementTextSchema, retrieves text content from the specified selector using Playwright's page.textContent method, and returns the text or '(empty)' if none.
    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 for validating input parameters of the get_element_text tool: selector (required string) 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 listTools response, defining name, description, and inputSchema matching the Zod schema.
    {
      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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't cover critical traits such as error handling (e.g., what happens if the selector doesn't match), performance implications, or return format details. This leaves significant gaps for an agent to understand 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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent 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 (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action but lacks details on behavior, usage context, and output, which are needed for full comprehension. It meets the minimum viable threshold but has clear gaps.

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, with clear docs for 'selector' and 'timeout'. The description adds no additional meaning beyond the schema, such as examples or edge cases. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 understandable. However, it doesn't explicitly differentiate from siblings like 'get_page_info' or 'evaluate_javascript', which might also retrieve text in different ways, so it doesn't reach the highest 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. With siblings like 'evaluate_javascript' that could extract text via scripts or 'get_page_info' that might include textual data, there's no indication of context, prerequisites, or exclusions for this specific tool.

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/AutoProbeMCP'

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