Skip to main content
Glama

get_url

Retrieves the current page URL during browser automation sessions to enable navigation tracking, link verification, and web scraping workflows.

Instructions

Get the current page URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute function (handler) for the 'get_url' tool. It calls the browser's getUrl method and returns the URL in a standardized success response format.
    handler: async () => {
      const url = await browser.getUrl();
      return { success: true, data: { url }, message: `Current URL: ${url}` };
    }
  • The input schema for the 'get_url' tool, which takes no parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • Registration of the 'get_url' tool as an object in the array returned by createPlaywrightTools(browser), making it available for MCP.
    {
      name: 'get_url',
      description: 'Get the current page URL',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
      handler: async () => {
        const url = await browser.getUrl();
        return { success: true, data: { url }, message: `Current URL: ${url}` };
      }
    },
  • Supporting helper method getUrl on the SimpleBrowser class used by the tool handler to retrieve the current page URL via Playwright API.
    async getUrl() {
      await this.ensureLaunched();
      return this.page.url();
    }
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 what the tool does but lacks details on behavior, such as whether it returns the full URL with query parameters, if it works only on certain page states, or if there are any latency or error-handling aspects. This is a significant gap for a tool with zero annotation coverage.

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. It is front-loaded with the core action ('Get the current page URL'), making it highly efficient and easy to parse. Every word earns its place, achieving optimal conciseness.

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. It doesn't specify what the return value looks like (e.g., string format, error cases) or behavioral constraints, which are crucial for an agent to use the tool effectively. For a simple tool, more context is needed to compensate for the missing structured data.

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 schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids unnecessary details. A baseline of 4 is applied as per the rules for zero-parameter tools, since no compensation is needed.

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 ('current page URL'), making the purpose immediately understandable. It distinguishes from siblings like get_title (which retrieves the page title) and get_text (which retrieves text content). However, it doesn't specify the exact scope or format of the URL returned, keeping it from 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 mention if this should be used for navigation verification, logging, or other contexts, nor does it reference sibling tools like navigate or get_title that might be used in related scenarios. This leaves the agent without explicit usage context.

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