Skip to main content
Glama

go_back

Navigate to the previous page in browser history using the Steel MCP Server's web navigation tool for Puppeteer-based browsing.

Instructions

Go back to the previous page in the browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'go_back' tool. It calls page.goBack() with waitUntil 'domcontentloaded' and returns success or error based on whether there was a previous page.
    async function handleGoBack(page: Page): Promise<CallToolResult> {
      const response = await page.goBack({ waitUntil: "domcontentloaded" });
      if (!response) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: "Cannot go back. No previous page in the browser history.",
            },
          ],
        };
      }
    
      return {
        isError: false,
        content: [{ type: "text", text: "Went back to the previous page." }],
      };
    }
  • The input schema for the 'go_back' tool, which requires no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
  • src/index.ts:554-562 (registration)
    Registers the 'go_back' tool in the TOOLS array, including its name, description, and schema.
    {
      name: "go_back",
      description: "Go back to the previous page in the browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • The switch case in handleToolCall that routes 'go_back' calls to the handler function.
    case "go_back":
      result = await handleGoBack(page);
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose important behavioral aspects like whether this requires the browser to have history, what happens if there's no previous page, if it waits for page load, or any error conditions. The description is minimal beyond the core functionality.

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 complete core functionality with zero 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.

Completeness3/5

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

For a simple navigation tool with no parameters and no output schema, the description covers the basic purpose adequately. However, it lacks important context about behavioral constraints (history requirements, error conditions) and doesn't explain what the tool returns or any side effects, which would be helpful for an agent.

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 with 100% schema coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this parameterless tool.

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 clearly states the specific action ('go back') and the resource ('previous page in the browser history'), distinguishing it from siblings like navigate (which goes to a new URL) or scroll tools. It uses precise terminology that leaves no ambiguity about what the tool does.

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

Usage Guidelines4/5

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

The description implies usage context (when you want to return to a previous page in browser history), but doesn't explicitly state when not to use it or name alternatives. For example, it doesn't clarify if this only works after navigation actions or if it's equivalent to the browser's back button functionality.

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/steel-dev/steel-mcp-server'

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