Skip to main content
Glama

get_title

Retrieves the title of the current web page during browser automation sessions, enabling accurate page identification and navigation tracking.

Instructions

Get the current page title

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'get_title' MCP tool, including name, description, empty input schema, and inline handler that calls browser.getTitle() and returns formatted response.
    {
      name: 'get_title',
      description: 'Get the current page title',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
      handler: async () => {
        const title = await browser.getTitle();
        return { success: true, data: { title }, message: `Page title: ${title}` };
      }
    },
  • The specific handler function executing the tool logic for 'get_title'.
    handler: async () => {
      const title = await browser.getTitle();
      return { success: true, data: { title }, message: `Page title: ${title}` };
    }
  • Input schema definition for 'get_title' tool (no required parameters).
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • Supporting helper method in SimpleBrowser class that launches browser if needed and retrieves the current page title using Playwright's page.title().
    async getTitle() {
      await this.ensureLaunched();
      return await this.page.title();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic function without mentioning whether this requires page loading, has latency considerations, returns structured data, or handles errors. For a tool with zero annotation coverage, this is insufficient.

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 communicates the core function without any wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

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 should provide more context about what the tool returns, error conditions, or dependencies. For a browser automation tool in a set with many siblings, the minimal description leaves significant gaps in understanding how to use it effectively.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the input requirements. The description appropriately doesn't add parameter information, which is correct for a parameterless tool, earning a baseline score of 4.

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 target resource ('the current page title'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_text' or 'get_url' that also retrieve page information, 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 like 'get_text' or 'get_url', nor does it mention any prerequisites or context for usage. It simply states what the tool does without addressing when it's appropriate.

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/zypin-testing/zypin-mcp'

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