Skip to main content
Glama
RonsDad
by RonsDad

browserbase_stagehand_extract

Extract structured data and text content from web pages using specific instructions and JSON schemas for scraping, information gathering, or content retrieval.

Instructions

Extracts structured information and text content from the current web page based on specific instructions and a defined schema. This tool is ideal for scraping data, gathering information, or pulling specific content from web pages. Use this tool when you need to get text content, data, or information from a page rather than interacting with elements. For interactive elements like buttons, forms, or clickable items, use the observe tool instead. The extraction works best when you provide clear, specific instructions about what to extract and a well-defined JSON schema for the expected output format. This ensures the extracted data is properly structured and usable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instructionYesThe specific instruction for what information to extract from the current page. Be as detailed and specific as possible about what you want to extract. For example: 'Extract all product names and prices from the listing page' or 'Get the article title, author, and publication date from this blog post'. The more specific your instruction, the better the extraction results will be. Avoid vague instructions like 'get everything' or 'extract the data'. Instead, be explicit about the exact elements, text, or information you need.

Implementation Reference

  • The main handler function that executes the extraction logic using stagehand.page.extract() based on the provided instruction.
    async function handleExtract(
      context: Context,
      params: ExtractInput,
    ): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        try {
          const stagehand = await context.getStagehand();
    
          const extraction = await stagehand.page.extract(params.instruction);
    
          return {
            content: [
              {
                type: "text",
                text: `Extracted content:\n${JSON.stringify(extraction, null, 2)}`,
              },
            ],
          };
        } catch (error) {
          const errorMsg = error instanceof Error ? error.message : String(error);
          throw new Error(`Failed to extract content: ${errorMsg}`);
        }
      };
    
      return {
        action,
        waitForNetwork: false,
      };
    }
  • Defines the input schema (ExtractInputSchema) and the tool schema (extractSchema) including name, description, and inputSchema.
    const ExtractInputSchema = z.object({
      instruction: z
        .string()
        .describe(
          "The specific instruction for what information to extract from the current page. " +
            "Be as detailed and specific as possible about what you want to extract. For example: " +
            "'Extract all product names and prices from the listing page' or 'Get the article title, " +
            "author, and publication date from this blog post'. The more specific your instruction, " +
            "the better the extraction results will be. Avoid vague instructions like 'get everything' " +
            "or 'extract the data'. Instead, be explicit about the exact elements, text, or information you need.",
        ),
    });
    
    type ExtractInput = z.infer<typeof ExtractInputSchema>;
    
    const extractSchema: ToolSchema<typeof ExtractInputSchema> = {
      name: "browserbase_stagehand_extract",
      description:
        "Extracts structured information and text content from the current web page based on specific instructions " +
        "and a defined schema. This tool is ideal for scraping data, gathering information, or pulling specific " +
        "content from web pages. Use this tool when you need to get text content, data, or information from a page " +
        "rather than interacting with elements. For interactive elements like buttons, forms, or clickable items, " +
        "use the observe tool instead. The extraction works best when you provide clear, specific instructions " +
        "about what to extract and a well-defined JSON schema for the expected output format. This ensures " +
        "the extracted data is properly structured and usable.",
      inputSchema: ExtractInputSchema,
    };
  • Registers the tool by creating the extractTool object with schema and handle, and exporting it as default.
    const extractTool: Tool<typeof ExtractInputSchema> = {
      capability: "core",
      schema: extractSchema,
      handle: handleExtract,
    };
    
    export default extractTool;
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 key traits: the tool extracts based on instructions and schema, works best with clear instructions, and ensures structured output. However, it lacks details on potential limitations (e.g., handling dynamic content, error cases, or performance aspects), which prevents a perfect score.

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 best practices. Each sentence adds value, such as distinguishing from 'observe' and advising on clear instructions. It could be slightly more concise by avoiding minor redundancy (e.g., repeating 'extract' concepts), but overall it's efficient.

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 (extraction from web pages with a single parameter) and lack of annotations or output schema, the description does a good job covering purpose, usage, and behavioral aspects. It mentions the need for a JSON schema for output, which partially compensates for the missing output schema. However, it doesn't detail return formats or error handling, leaving some gaps.

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?

The input schema has 100% description coverage, providing detailed guidance on the 'instruction' parameter. The description adds some context by emphasizing the need for clear, specific instructions and a well-defined JSON schema for output, but this mostly reinforces the schema's content rather than adding significant new semantic value beyond it.

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 with specific verbs ('extracts structured information and text content') and resources ('from the current web page'), distinguishing it from sibling tools like 'observe' for interactive elements. It explicitly mentions scraping data, gathering information, and pulling content, making the purpose unambiguous.

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 get text content, data, or information from a page') and when not to ('For interactive elements like buttons, forms, or clickable items, use the observe tool instead'). It also mentions ideal scenarios like scraping data and gathering information, offering clear alternatives.

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