Skip to main content
Glama

navigate

Navigate the active browser tab to a specified URL, enabling automated page loading and interaction for web tasks.

Instructions

Navigate the active tab to a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • The navigate handler function that receives a URL and uses Playwright's page.goto to navigate the active tab. Returns the resulting URL and page title.
    async function navigate(args: { url: string }) {
      const p = requirePage();
      await p.goto(args.url, { waitUntil: 'domcontentloaded', timeout: 20000 });
      return { url: p.url(), title: await p.title().catch(() => '') };
    }
  • The input schema for the navigate tool, defining url as a required string property.
    inputSchema: {
      type: 'object',
      properties: { url: { type: 'string' } },
      required: ['url'],
    },
  • src/index.ts:414-422 (registration)
    The tool registration within the TOOLS array, containing the name 'navigate' and its description.
    {
      name: 'navigate',
      description: 'Navigate the active tab to a URL.',
      inputSchema: {
        type: 'object',
        properties: { url: { type: 'string' } },
        required: ['url'],
      },
    },
  • src/index.ts:468-468 (registration)
    The switch-case dispatch routing the 'navigate' tool call to the navigate function.
    case 'navigate':     result = await navigate(args as { url: string }); break;
Behavior1/5

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

The description does not disclose behavioral traits. Without annotations, it should explain whether it waits for page load, returns a result, or has side effects like changing the active tab. The single sentence gives no such details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with one sentence. However, it is too brief, omitting essential details. It is front-loaded but under-specified, sacrificing clarity for brevity.

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 tool's simplicity, the description is incomplete. It lacks output schema information, error handling cues, and context about when the tool is applicable. An agent would need additional assumptions to use it correctly.

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

Parameters1/5

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

The only parameter 'url' has no description in the schema (0% coverage) and the tool description adds no meaning. It does not specify format, required protocol, or whether relative URLs are accepted.

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 (navigate) and the resource (active tab to a URL). It distinguishes the tool from sibling tools like click, type, and screenshot, which have different purposes. However, it could be more specific about scope, e.g., whether it supports local files or only HTTP URLs.

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?

No guidance is provided on when to use navigate versus alternatives such as click on a link or list_tabs. There is no mention of prerequisites like ensuring a tab exists or that the URL is valid.

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/flying-pisces/mcp-helm'

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