Skip to main content
Glama

pilot_back

Navigate back in browser history to return to previous web pages during automated browsing sessions.

Instructions

Go back in browser history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the pilot_back tool, which navigates the browser back one page in history.
    async () => {
      await bm.ensureBrowser();
      try {
        const page = bm.getPage();
        await page.goBack({ waitUntil: 'domcontentloaded', timeout: 15000 });
        bm.resetFailures();
        return { content: [{ type: 'text' as const, text: `Back → ${page.url()}` }] };
      } catch (err) {
        bm.incrementFailures();
        return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
      }
    }
  • MCP tool registration for pilot_back.
    server.tool(
      'pilot_back',
      'Go back in browser history.',
      {},
      async () => {
        await bm.ensureBrowser();
        try {
          const page = bm.getPage();
          await page.goBack({ waitUntil: 'domcontentloaded', timeout: 15000 });
          bm.resetFailures();
          return { content: [{ type: 'text' as const, text: `Back → ${page.url()}` }] };
        } catch (err) {
          bm.incrementFailures();
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. States the navigation action but omits edge cases (e.g., behavior when no history exists) and whether operation waits for navigation to complete or returns previous page data.

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?

Four words, zero redundancy. Immediately delivers core function without preamble or wasted language.

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?

Sufficient for a 0-parameter navigation primitive, but gaps remain regarding error conditions and relationship to pilot_forward. Adequate but minimal.

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?

Zero parameters present; baseline 4 applies per rubric. No parameter documentation 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?

States specific action (go back) and resource (browser history) clearly. Lacks explicit differentiation from siblings like pilot_navigate or pilot_forward, though implied by directionality.

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?

Provides no guidance on when to use this versus pilot_navigate (for direct URL navigation) or prerequisites (requires history). No 'when-not' or alternative mentioned.

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/TacosyHorchata/Pilot'

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