Skip to main content
Glama

cdp_send

Send commands to Chrome DevTools Protocol for browser automation, enabling navigation, DOM manipulation, and JavaScript execution through direct CDP method calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesCDP method (e.g., 'Page.navigate', 'DOM.getDocument', 'Runtime.evaluate')
paramsNoParameters object for the CDP method

Implementation Reference

  • server.js:41-59 (handler)
    Handler function for the 'cdp_send' tool. Ensures browser/CDP session is ready, sends the specified CDP method with params, returns JSON stringified result or error.
    async ({ method, params }) => {
      const { cdp } = await ensureBrowser();
      try {
        const result = await cdp.send(method, params || {});
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({ error: error.message }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for 'cdp_send' tool using Zod: required 'method' string and optional 'params' object.
    {
      method: z
        .string()
        .describe("CDP method (e.g., 'Page.navigate', 'DOM.getDocument', 'Runtime.evaluate')"),
      params: z
        .record(z.unknown())
        .optional()
        .describe("Parameters object for the CDP method"),
    },
  • server.js:28-60 (registration)
    Registration of the 'cdp_send' tool with MCP server.tool, including schema and handler.
    // Core tool: Raw CDP method - call ANY Chrome DevTools Protocol method
    // Reference: https://chromedevtools.github.io/devtools-protocol/
    server.tool(
      "cdp_send",
      {
        method: z
          .string()
          .describe("CDP method (e.g., 'Page.navigate', 'DOM.getDocument', 'Runtime.evaluate')"),
        params: z
          .record(z.unknown())
          .optional()
          .describe("Parameters object for the CDP method"),
      },
      async ({ method, params }) => {
        const { cdp } = await ensureBrowser();
        try {
          const result = await cdp.send(method, params || {});
          return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({ error: error.message }, null, 2),
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper function ensureBrowser() that launches Chromium browser, creates a page, and initializes CDP session if not already done. Used by cdp_send handler.
    async function ensureBrowser() {
      if (!browser) {
        browser = await chromium.launch({
          headless: false,
          args: ["--disable-web-security", "--allow-running-insecure-content"],
        });
        page = await browser.newPage();
        cdp = await page.context().newCDPSession(page);
      }
      return { browser, page, cdp };
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/Myestery/browser-cdp-mcp'

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