Skip to main content
Glama

browser_title

Retrieve the current web page title during browser automation to verify page loading or extract page information.

Instructions

Get the current page title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler function for the 'browser_title' tool. It retrieves the current browser driver from the state manager, fetches the page title using driver.getTitle(), and returns it in the MCP response format, with error handling.
    server.tool('browser_title', 'Get the current page title', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        const title = await driver.getTitle();
        return {
          content: [{ type: 'text', text: `Current page title is: ${title}` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting page title: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • Registration of the 'browser_title' tool using server.tool, with no input schema ({}), description 'Get the current page title', and inline handler.
    server.tool('browser_title', 'Get the current page title', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        const title = await driver.getTitle();
        return {
          content: [{ type: 'text', text: `Current page title is: ${title}` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error getting page title: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
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 ('Get') but doesn't describe traits such as whether it's read-only (implied but not stated), potential errors (e.g., if no page is open), performance characteristics, or return format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get the current page title') with zero waste. It's front-loaded with the core action and resource, making it highly concise and well-structured for quick understanding.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, usage context, or return values. For a simple read operation, it's passable but leaves gaps that could hinder an agent's effective use.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline of 4 for zero-parameter tools. No additional semantic value is required or provided.

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 'Get the current page title' clearly states the verb ('Get') and resource ('current page title'), making the purpose specific and understandable. It distinguishes itself from siblings like 'browser_get_url' or 'browser_get_page_source' by focusing on the title. However, it doesn't explicitly differentiate from potential similar tools (e.g., if there were a 'browser_get_metadata' tool), so it falls short of 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. It doesn't mention prerequisites (e.g., requiring an open browser page), exclusions, or comparisons to siblings like 'browser_get_url' for retrieving other page information. Usage is implied by the name and purpose, but explicit context is lacking.

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