Skip to main content
Glama
maderwin

pinchtab-mcp

Navigate

pinchtab_navigate

Navigate to a URL with optional wait time, and automatically return a compact page snapshot after load.

Instructions

Navigate the browser to a URL. Set waitMs to wait for page load and get a snapshot back automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
newTabNoOpen the URL in a new tab instead of navigating the current one.
urlYesURL to navigate to
waitMsNoWait this many ms after navigation, then return a compact page snapshot (max 10000).

Implementation Reference

  • The handler function that executes the pinchtab_navigate tool logic. It sends a POST to /navigate (or /tab with new) via the pinch client, optionally waits for a snapshot, and returns the result.
    async ({ url, newTab, waitMs }) => {
      try {
        if (newTab) {
          await pinch("POST", "/tab", { action: "new", url });
        } else {
          await pinch("POST", "/navigate", { url });
        }
        if (waitMs && waitMs > 0) {
          const snap = await waitAndSnapshot(waitMs);
          return toolResult(`Navigated to ${url}\n\n${snap}`);
        }
        return toolResult({ navigated: url });
      } catch (error) {
        return toolError(error);
      }
    },
  • Input schema definition for pinchtab_navigate: url (string, required), newTab (boolean, optional), waitMs (number, optional, max 10000ms).
    {
      description:
        "Navigate the browser to a URL. Set waitMs to wait for page load and get a snapshot back automatically.",
      inputSchema: z.object({
        newTab: z
          .boolean()
          .optional()
          .describe("Open the URL in a new tab instead of navigating the current one."),
        url: z.string().describe("URL to navigate to"),
        waitMs: z
          .number()
          .optional()
          .describe(
            "Wait this many ms after navigation, then return a compact page snapshot (max 10000).",
          ),
      }),
      title: "Navigate",
    },
  • Tool registration: registerNavigationTools calls server.registerTool('pinchtab_navigate', ...) with the schema and handler.
    export function registerNavigationTools(server: McpServer) {
      server.registerTool(
        "pinchtab_navigate",
        {
          description:
            "Navigate the browser to a URL. Set waitMs to wait for page load and get a snapshot back automatically.",
          inputSchema: z.object({
            newTab: z
              .boolean()
              .optional()
              .describe("Open the URL in a new tab instead of navigating the current one."),
            url: z.string().describe("URL to navigate to"),
            waitMs: z
              .number()
              .optional()
              .describe(
                "Wait this many ms after navigation, then return a compact page snapshot (max 10000).",
              ),
          }),
          title: "Navigate",
        },
        async ({ url, newTab, waitMs }) => {
          try {
            if (newTab) {
              await pinch("POST", "/tab", { action: "new", url });
            } else {
              await pinch("POST", "/navigate", { url });
            }
            if (waitMs && waitMs > 0) {
              const snap = await waitAndSnapshot(waitMs);
              return toolResult(`Navigated to ${url}\n\n${snap}`);
            }
            return toolResult({ navigated: url });
          } catch (error) {
            return toolError(error);
          }
        },
      );
  • registerAllTools calls registerNavigationTools(server) to wire up the tool.
    export function registerAllTools(server: McpServer) {
      registerInstanceTools(server);
      registerNavigationTools(server);
      registerInteractionTools(server);
      registerContentTools(server);
    }
  • waitAndSnapshot helper used by the handler when waitMs is provided: waits the specified ms (clamped to 10s) and returns a compact snapshot.
    export async function waitAndSnapshot(ms: number): Promise<string> {
      const clamped = Math.min(ms, MAX_WAIT_MS);
      await new Promise((resolve) => setTimeout(resolve, clamped));
      const snapshot = await pinch("GET", "/snapshot?format=compact");
      return typeof snapshot === "string" ? snapshot : JSON.stringify(snapshot, undefined, 2);
    }
Behavior3/5

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

The description discloses that setting waitMs will return a snapshot after waiting. Without annotations, this helps the agent understand part of the behavior. However, it does not specify the return value when waitMs is omitted, error handling, or any side effects like tab focus changes.

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 extremely concise, using only two sentences to convey the core action, option, and automatic snapshot behavior. No unnecessary words, and the key information is front-loaded.

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?

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description covers the main functionality but misses details like what happens on navigation failure, the format of the snapshot, and the behavior without waitMs. It is adequate but not fully comprehensive.

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 description adds meaningful context for the waitMs parameter by explaining it triggers a snapshot, which is not evident from the schema alone. The other parameters are well-documented in the schema (url required, newTab description), so the description complements them adequately.

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 tool navigates the browser to a URL, which is its primary purpose. While there is no explicit differentiation from sibling tools, the name and description are unambiguous and unique among the listed siblings.

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 mentions setting waitMs for waiting and getting a snapshot, giving some guidance on when to use that parameter. However, it does not provide context on when to use newTab, nor does it contrast with other navigation-related tools or mention prerequisites.

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/maderwin/pinchtab-mcp'

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