Skip to main content
Glama
RonsDad
by RonsDad

browserbase_stagehand_observe

Identifies interactive elements like buttons, links, and form fields on web pages to prepare for subsequent automated actions.

Instructions

Observes and identifies specific interactive elements on the current web page that can be used for subsequent actions. This tool is specifically designed for finding actionable (interactable) elements such as buttons, links, form fields, dropdowns, checkboxes, and other UI components that you can interact with. Use this tool when you need to locate elements before performing actions with the act tool. DO NOT use this tool for extracting text content or data - use the extract tool instead for that purpose. The observe tool returns detailed information about the identified elements including their properties, location, and interaction capabilities. This information can then be used to craft precise actions. The more specific your observation instruction, the more accurate the element identification will be. Think of this as your 'eyes' on the page to find exactly what you need to interact with.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instructionYesDetailed instruction for what specific elements or components to observe on the web page. This instruction must be extremely specific and descriptive. For example: 'Find the red login button in the top right corner', 'Locate the search input field with placeholder text', or 'Identify all clickable product cards on the page'. The more specific and detailed your instruction, the better the observation results will be. Avoid generic instructions like 'find buttons' or 'see elements'. Instead, describe the visual characteristics, location, text content, or functionality of the elements you want to observe. This tool is designed to help you identify interactive elements that you can later use with the act tool for performing actions like clicking, typing, or form submission.
returnActionNoWhether to return the action to perform on the element. If true, the action will be returned as a string. If false, the action will not be returned.

Implementation Reference

  • The handleObserve function implements the core logic of the 'browserbase_stagehand_observe' tool. It retrieves the stagehand instance from context and calls stagehand.page.observe with the instruction and optional returnAction flag, then formats the observations as a text content result.
    async function handleObserve(
      context: Context,
      params: ObserveInput,
    ): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        try {
          const stagehand = await context.getStagehand();
    
          const observations = await stagehand.page.observe({
            instruction: params.instruction,
            returnAction: params.returnAction,
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Observations: ${JSON.stringify(observations)}`,
              },
            ],
          };
        } catch (error) {
          const errorMsg = error instanceof Error ? error.message : String(error);
          throw new Error(`Failed to observe: ${errorMsg}`);
        }
      };
    
      return {
        action,
        waitForNetwork: false,
      };
    }
  • The tool schema defining the name 'browserbase_stagehand_observe', detailed description, and input schema (ObserveInputSchema defined earlier in the file).
    const observeSchema: ToolSchema<typeof ObserveInputSchema> = {
      name: "browserbase_stagehand_observe",
      description:
        "Observes and identifies specific interactive elements on the current web page that can be used for subsequent actions. " +
        "This tool is specifically designed for finding actionable (interactable) elements such as buttons, links, form fields, " +
        "dropdowns, checkboxes, and other UI components that you can interact with. Use this tool when you need to locate " +
        "elements before performing actions with the act tool. DO NOT use this tool for extracting text content or data - " +
        "use the extract tool instead for that purpose. The observe tool returns detailed information about the identified " +
        "elements including their properties, location, and interaction capabilities. This information can then be used " +
        "to craft precise actions. The more specific your observation instruction, the more accurate the element identification " +
        "will be. Think of this as your 'eyes' on the page to find exactly what you need to interact with.",
      inputSchema: ObserveInputSchema,
    };
  • The observeTool is included in the exported TOOLS array, which collects all available tools for registration in the MCP server.
    export const TOOLS = [
      ...multiSessionTools,
      ...sessionTools,
      navigateTool,
      actTool,
      extractTool,
      observeTool,
      screenshotTool,
      getUrlTool,
    ];
  • src/index.ts:196-226 (registration)
    The TOOLS array (including observeTool) is spread into 'tools' and each tool is registered on the MCP server via server.tool() using its schema.name. The handler is wrapped to call context.run(tool, params), which invokes the tool's handle function.
    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}`,
        );
      }
    });
  • The observeTool object is created by combining the schema and handle function, and exported for use in higher-level tool registries.
    const observeTool: Tool<typeof ObserveInputSchema> = {
      capability: "core",
      schema: observeSchema,
      handle: handleObserve,
    };
    
    export default observeTool;
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it returns 'detailed information about the identified elements including their properties, location, and interaction capabilities,' which can be used to 'craft precise actions.' It also notes that 'the more specific your observation instruction, the more accurate the element identification will be,' adding useful context about performance. However, it lacks details on potential limitations, such as error handling or timeouts.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose, followed by usage guidelines and behavioral details. Most sentences add value, such as distinguishing from siblings and explaining parameter impact. However, it could be slightly more concise by avoiding minor repetition, like reiterating the tool's role as 'eyes' on the page.

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 element identification) and lack of annotations or output schema, the description does a good job of covering purpose, usage, and behavior. It explains what the tool does, when to use it, and what it returns. However, without an output schema, it could benefit from more details on the return format or examples of output, though the description partially compensates by mentioning 'properties, location, and interaction capabilities.'

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds value by emphasizing the importance of specificity in the 'instruction' parameter ('The more specific your observation instruction, the more accurate the element identification will be') and linking it to the tool's purpose ('Think of this as your 'eyes' on the page'). While it doesn't explain parameters beyond the schema, it provides context that enhances understanding.

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: 'Observes and identifies specific interactive elements on the current web page that can be used for subsequent actions.' It specifies the verb ('observes and identifies'), resource ('interactive elements'), and scope ('on the current web page'), and distinguishes it from sibling tools like 'extract' for text content.

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 ('when you need to locate elements before performing actions with the act tool') and when not to use it ('DO NOT use this tool for extracting text content or data - use the extract tool instead'). It clearly distinguishes between this tool and its alternatives, including 'act' and '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/RonsDad/mcp-server-browserbase'

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