Skip to main content
Glama

get_text

Extract text content from web page elements using CSS selectors for browser automation with Playwright MCP.

Instructions

Get text content from an element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
page_idNo

Implementation Reference

  • The main handler for the 'get_text' tool within the tool dispatcher. It retrieves the text content from the specified selector on the active Playwright page.
    elif name == "get_text":
        selector = arguments.get("selector")
        if not selector:
            raise ValueError("Selector is required")
            
        page = get_active_page(arguments.get("page_id"))
        text = await page.text_content(selector)
        return [types.TextContent(type="text", text=text or "")]
  • Registers the 'get_text' tool in the list_tools handler, including its name, description, and input schema.
    types.Tool(
        name="get_text",
        description="Get text content from an element",
        inputSchema={
            "type": "object",
            "properties": {
                "selector": {"type": "string"},
                "page_id": {"type": "string"},
            },
            "required": ["selector"],
        },
    ),
  • Defines the input schema for the 'get_text' tool, requiring a 'selector' and optionally 'page_id'.
    inputSchema={
        "type": "object",
        "properties": {
            "selector": {"type": "string"},
            "page_id": {"type": "string"},
        },
        "required": ["selector"],
    },
  • Helper function used by the get_text handler to resolve the Playwright Page instance from page_id or default.
    def get_active_page(page_id: Optional[str] = None) -> Page:
        """Get the active page based on page_id or current default."""
        global current_page_id
        
        if page_id is None:
            page_id = current_page_id
        
        if page_id not in pages:
            raise ValueError(f"Page not found: {page_id}")
        
        return pages[page_id]
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. It states 'Get text content' but doesn't disclose behavioral traits such as what happens if the element isn't found, if it requires a loaded page, or the format of returned text. This leaves significant gaps for a tool with parameters.

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 no wasted words, making it highly concise and front-loaded. It efficiently states the core function 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 no annotations, 0% schema coverage, no output schema, and 2 parameters, the description is incomplete. It doesn't explain return values, error handling, or parameter usage, making it inadequate for effective tool invocation in this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema only provides types without meanings. The description doesn't add any semantic information about parameters like 'selector' or 'page_id', such as what they represent or how to use them, failing to compensate for the low coverage.

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 action ('Get') and resource ('text content from an element'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_page_content' or 'get_pages', which also retrieve content, so it's not fully specific to sibling context.

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 like 'get_page_content' or 'get_pages', nor does it mention prerequisites such as needing a page to be loaded. It's a basic statement without context for selection.

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/misanthropic-ai/playwrite-mcp'

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