Skip to main content
Glama

browser_navigate_forward

Read-only

Navigate forward to the next page in browser history during web automation tasks.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'browser_navigate_forward' that performs the forward navigation in the browser tab using Playwright's page.goForward() method, includes a snapshot in the response, and adds the corresponding code snippet.
    handle: async (tab, params, response) => {
      await tab.page.goForward();
      response.setIncludeSnapshot();
      response.addCode(`await page.goForward();`);
    },
  • Schema definition for the 'browser_navigate_forward' tool, specifying name, title, description, empty input schema, and readOnly type.
    schema: {
      name: 'browser_navigate_forward',
      title: 'Go forward',
      description: 'Go forward to the next page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • Exports the 'browser_navigate_forward' tool (as goForward) along with others for inclusion in the central tools list.
    export default [
      navigate,
      goBack,
      goForward,
    ];
  • src/tools.ts:36-52 (registration)
    Central registration of all tools, spreading the navigate tools (including browser_navigate_forward) into the allTools array used by the MCP server backend.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
Behavior4/5

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

Annotations provide readOnlyHint=true, destructiveHint=false, and openWorldHint=true, indicating a safe, non-destructive operation. The description adds context by specifying 'to the next page,' which clarifies the scope of navigation. However, it does not detail behavioral aspects like what happens if no forward history exists or if it's idempotent.

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 directly states the tool's function without any unnecessary words. It is front-loaded and perfectly sized for its purpose, earning its place with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and rich annotations, the description is mostly complete. It specifies the navigation direction, but could improve by mentioning constraints (e.g., requires forward history) or response behavior, though annotations cover safety aspects well.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. A baseline of 4 is applied as it adequately handles the lack of parameters without redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Go forward to the next page' clearly states the action (go forward) and the resource (next page) with a specific verb. It distinguishes itself from sibling tools like 'browser_navigate_back' by specifying the forward direction, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage in a browser navigation context but does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites (e.g., requiring a forward history) or exclusions, leaving usage context inferred rather than clearly defined.

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/maywzh/playwright-mcp'

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