Skip to main content
Glama
Xxx00xxX33

Browserbase MCP Server

by Xxx00xxX33

browserbase_stagehand_act

Execute specific web page interactions like clicking buttons or typing text through browser automation.

Instructions

Performs an action on a web page element. Act actions should be as atomic and specific as possible, i.e. "Click the sign in button" or "Type 'hello' into the search input". AVOID actions that are more than one step, i.e. "Order me pizza" or "Send an email to Paul asking him to call me".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform. Should be as atomic and specific as possible, i.e. 'Click the sign in button' or 'Type 'hello' into the search input'. AVOID actions that are more than one step, i.e. 'Order me pizza' or 'Send an email to Paul asking him to call me'. The instruction should be just as specific as possible, and have a strong correlation to the text on the page. If unsure, use observe before using act.
variablesNoVariables used in the action template. ONLY use variables if you're dealing with sensitive data or dynamic content. For example, if you're logging in to a website, you can use a variable for the password. When using variables, you MUST have the variable key in the action template. For example: {"action": "Fill in the password", "variables": {"password": "123456"}}

Implementation Reference

  • The main handler function that executes the tool by calling stagehand.page.act() with the provided action and variables.
    async function handleAct(
      context: Context,
      params: ActInput,
    ): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        try {
          const stagehand = await context.getStagehand();
    
          await stagehand.page.act({
            action: params.action,
            variables: params.variables,
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Action performed: ${params.action}`,
              },
            ],
          };
        } catch (error) {
          const errorMsg = error instanceof Error ? error.message : String(error);
          throw new Error(`Failed to perform action: ${errorMsg}`);
        }
      };
    
      return {
        action,
        waitForNetwork: false,
      };
    }
  • Defines the Zod input schema for the action and variables, and the tool schema with name 'browserbase_stagehand_act'.
    const ActInputSchema = z.object({
      action: z
        .string()
        .describe(
          "The action to perform. Should be as atomic and specific as possible, " +
            "i.e. 'Click the sign in button' or 'Type 'hello' into the search input'. AVOID actions that are more than one " +
            "step, i.e. 'Order me pizza' or 'Send an email to Paul asking him to call me'. The instruction should be just as specific as possible, " +
            "and have a strong correlation to the text on the page. If unsure, use observe before using act.",
        ),
      variables: z
        .object({})
        .optional()
        .describe(
          "Variables used in the action template. ONLY use variables if you're dealing " +
            "with sensitive data or dynamic content. For example, if you're logging in to a website, " +
            "you can use a variable for the password. When using variables, you MUST have the variable " +
            'key in the action template. For example: {"action": "Fill in the password", "variables": {"password": "123456"}}',
        ),
    });
    
    type ActInput = z.infer<typeof ActInputSchema>;
    
    const actSchema: ToolSchema<typeof ActInputSchema> = {
      name: "browserbase_stagehand_act",
      description:
        "Performs an action on a web page element. Act actions should be as atomic and " +
        'specific as possible, i.e. "Click the sign in button" or "Type \'hello\' into the search input". ' +
        'AVOID actions that are more than one step, i.e. "Order me pizza" or "Send an email to Paul ' +
        'asking him to call me".',
      inputSchema: ActInputSchema,
    };
  • src/tools/act.ts:71-75 (registration)
    Creates and exports the actTool object that bundles the schema and handler.
    const actTool: Tool<typeof ActInputSchema> = {
      capability: "core",
      schema: actSchema,
      handle: handleAct,
    };
  • Includes the actTool in the TOOLS array exported for use in MCP server registration.
    export const TOOLS = [
      ...multiSessionTools,
      ...sessionTools,
      navigateTool,
      actTool,
      extractTool,
      observeTool,
      screenshotTool,
    ];
  • src/index.ts:188-218 (registration)
    Registers all tools from the TOOLS array to the MCP server by calling server.tool() for each, including browserbase_stagehand_act.
    const tools: MCPToolsArray = [...TOOLS];
    
    // Register each tool with the Smithery server
    tools.forEach((tool) => {
      if (tool.schema.inputSchema instanceof z.ZodObject) {
        server.tool(
          tool.schema.name,
          tool.schema.description,
          tool.schema.inputSchema.shape,
          async (params: z.infer<typeof tool.schema.inputSchema>) => {
            try {
              const result = await context.run(tool, params);
              return result;
            } catch (error) {
              const errorMessage =
                error instanceof Error ? error.message : String(error);
              process.stderr.write(
                `[Smithery Error] ${new Date().toISOString()} Error running tool ${tool.schema.name}: ${errorMessage}\n`,
              );
              throw new Error(
                `Failed to run tool '${tool.schema.name}': ${errorMessage}`,
              );
            }
          },
        );
      } else {
        console.warn(
          `Tool "${tool.schema.name}" has an input schema that is not a ZodObject. Schema type: ${tool.schema.inputSchema.constructor.name}`,
        );
      }
    });
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the tool's behavioral traits well: it performs actions on web elements, emphasizes atomicity, and advises using 'observe' first. However, it lacks details on error handling, performance characteristics, or what happens if the element isn't found, leaving some behavioral aspects unclear.

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 concise and well-structured: it states the purpose in the first sentence, provides usage guidelines with clear examples and anti-examples, and avoids redundancy. Every sentence adds value without unnecessary elaboration.

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?

Given the tool's complexity (interactive web actions) and lack of annotations or output schema, the description is mostly complete. It covers purpose, usage, and behavioral traits effectively. However, it could improve by mentioning potential side effects or dependencies on prior steps like navigation, but it's sufficient for an agent to use the tool correctly.

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 fully documents both parameters. The description adds minimal value beyond the schema, as it repeats the same examples and guidelines for the 'action' parameter. It doesn't provide additional context or semantics not already covered in the schema descriptions.

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 tool's purpose: 'Performs an action on a web page element.' It specifies the verb ('performs an action') and resource ('web page element'), and distinguishes it from siblings like 'observe' or 'navigate' by focusing on interactive actions rather than observation or navigation.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: for atomic, specific actions like clicking buttons or typing text. It explicitly advises against multi-step actions and suggests using 'observe' before 'act' if unsure, clearly differentiating it from alternatives like 'navigate' or 'extract'.

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/Xxx00xxX33/mcp-server-browserbase'

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