Skip to main content
Glama
BrowserGenie

BrowserGenie MCP Server

by BrowserGenie

read_page_html

Retrieve the complete HTML source of the currently active browser tab to inspect page structure and content.

Instructions

Read the full HTML source of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTarget tab ID (defaults to active tab)
apiKeyNoAPI key for authentication

Implementation Reference

  • Registers the 'read_page_html' MCP tool with the server, defining its name, description, input schema (optional tabId and apiKey), and handler that sends a command via WebSocket bridge.
    export function registerDevtoolsSourcesTools(server: McpServer, bridge: WebSocketBridge) {
      server.tool(
        'read_page_html',
        'Read the full HTML source of the current page',
        {
          tabId: z.number().optional().describe('Target tab ID (defaults to active tab)'),
          apiKey: z.string().optional().describe('API key for authentication'),
        },
        async ({ tabId, apiKey }) => {
          const result = await bridge.sendCommand({
            command: 'read_page_html',
            params: {},
            tabId,
            apiKey,
          });
          if (!result.success) {
            return { content: [{ type: 'text', text: `Error: ${result.error?.message}` }], isError: true };
          }
          return { content: [{ type: 'text', text: result.data as string }] };
        }
      );
  • The handler function that executes the tool: sends a 'read_page_html' command via WebSocketBridge.sendCommand and returns the HTML as text, or an error message if the command fails.
    async ({ tabId, apiKey }) => {
      const result = await bridge.sendCommand({
        command: 'read_page_html',
        params: {},
        tabId,
        apiKey,
      });
      if (!result.success) {
        return { content: [{ type: 'text', text: `Error: ${result.error?.message}` }], isError: true };
      }
      return { content: [{ type: 'text', text: result.data as string }] };
    }
  • Input schema for the tool: tabId (optional number) and apiKey (optional string), validated with Zod.
    {
      tabId: z.number().optional().describe('Target tab ID (defaults to active tab)'),
      apiKey: z.string().optional().describe('API key for authentication'),
    },
  • The WebSocketBridge.sendCommand method that forwards the 'read_page_html' command to the Chrome extension via WebSocket and returns the response.
    async sendCommand(cmd: BridgeCommand): Promise<BridgeResponse> {
      if (!this.isConnected()) {
        return {
          success: false,
          error: {
            code: 'NOT_CONNECTED',
            message: 'Chrome extension is not connected. Ensure the extension is installed, enabled, and the browser is running.',
          },
        };
      }
    
      const id = crypto.randomUUID();
      const timeout = cmd.timeout ?? DEFAULT_TIMEOUT;
    
      return new Promise<BridgeResponse>((resolve, reject) => {
        const timer = setTimeout(() => {
          this.pending.delete(id);
          resolve({
            success: false,
            error: {
              code: 'TIMEOUT',
              message: `Command '${cmd.command}' timed out after ${timeout}ms`,
            },
          });
        }, timeout);
    
        this.pending.set(id, { resolve, reject, timer });
    
        const message = {
          id,
          type: 'request',
          command: cmd.command,
          params: cmd.params,
          tabId: cmd.tabId,
          apiKey: cmd.apiKey,
          timestamp: Date.now(),
        };
    
        this.client!.send(JSON.stringify(message));
      });
    }
  • Import of registerDevtoolsSourcesTools from devtools-sources.ts, called at line 39 to register the tool.
    import { registerDevtoolsSourcesTools } from './devtools-sources.js';
Behavior3/5

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

The description implies a non-destructive read operation but lacks details on authentication requirements, error handling, or behavior for invalid tab IDs. With no annotations, the description carries full burden but provides minimal behavioral context.

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 single-sentence description is extremely concise with no wasted words. It efficiently conveys the tool's purpose.

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?

For a simple read operation with no output schema, the description is mostly complete. It could optionally mention that the tool returns the HTML source, but the tool name and description make this implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides.

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 verb 'Read', the resource 'full HTML source', and the scope 'current page'. It distinguishes this tool from siblings like read_page_resources, read_scripts, and read_stylesheets which read other resources.

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 this tool instead of alternatives. There is no mention of prerequisites, context, or when not to use it.

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/BrowserGenie/mcp'

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