Skip to main content
Glama
autopilotbrowser

Autopilot Browser MCP Server

Official

search_workflows

Find automated browser workflows for web scraping, data extraction, and automation tasks by searching with keywords.

Instructions

Search for available Autopilot Browser workflows by keyword. Returns a list of workflows that match the search term. If no search term is provided, returns all workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchTermNoOptional keyword to search for specific workflows (e.g., 'scraping', 'automation', 'data extraction')

Implementation Reference

  • Executes the search_workflows tool by extracting optional searchTerm from input arguments, calling the apiClient helper, formatting results as JSON text content, and handling errors.
    if (request.params.name === "search_workflows") {
      const { searchTerm } = request.params.arguments as {
        searchTerm?: string;
      };
    
      try {
        const workflows = await apiClient.searchWorkflows(searchTerm);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(workflows, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error searching workflows: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the search_workflows tool, specifying an optional 'searchTerm' string property.
      inputSchema: {
        type: "object",
        properties: {
          searchTerm: {
            type: "string",
            description: "Optional keyword to search for specific workflows (e.g., 'scraping', 'automation', 'data extraction')",
          },
        },
      },
    },
  • src/index.ts:129-141 (registration)
    Tool registration in the MCP server's ListTools handler, including name, description, and input schema for search_workflows.
    {
      name: "search_workflows",
      description: "Search for available Autopilot Browser workflows by keyword. Returns a list of workflows that match the search term. If no search term is provided, returns all workflows.",
      inputSchema: {
        type: "object",
        properties: {
          searchTerm: {
            type: "string",
            description: "Optional keyword to search for specific workflows (e.g., 'scraping', 'automation', 'data extraction')",
          },
        },
      },
    },
  • Core helper function in AutopilotAPIClient class that performs the actual HTTP GET request to the Autopilot Browser API's /wf/search endpoint to fetch workflows.
    async searchWorkflows(searchTerm?: string) {
      const url = new URL(`${this.baseUrl}/wf/search`);
      if (searchTerm) {
        url.searchParams.append('searchTerm', searchTerm);
      }
    
      const response = await fetch(url.toString(), {
        method: 'GET',
        headers: {
          'x-api-key': this.apiKey,
          'Content-Type': 'application/json',
        },
      });
      
      if (!response.ok) {
        throw new Error(`API Error: ${response.status} ${response.statusText}`);
      }
      
      return await response.json();
    }
Behavior2/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 of behavioral disclosure. It states the tool returns a list of workflows, which is basic output information, but it doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior, or error handling. The description is minimal and lacks rich 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 description is concise and well-structured with two sentences: the first states the purpose and basic behavior, and the second clarifies the optional parameter's effect. Every sentence earns its place, and there is no wasted text, making it easy to understand quickly.

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

Completeness3/5

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

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose and parameter usage, but without annotations or output schema, it lacks details on behavioral traits, return format, and error handling. The description is complete enough for a simple search tool but could be more informative.

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, with the parameter 'searchTerm' well-documented as an optional keyword. The description adds marginal value by reinforcing that the search term is optional and providing examples ('e.g., 'scraping', 'automation', 'data extraction''), but it doesn't add significant meaning beyond what the schema already provides. Baseline 3 is appropriate given high schema coverage.

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

Purpose4/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: 'Search for available Autopilot Browser workflows by keyword.' It specifies the verb ('search'), resource ('Autopilot Browser workflows'), and scope ('by keyword'). However, it doesn't explicitly differentiate from the sibling tool 'run_workflow' beyond their different functions.

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

Usage Guidelines3/5

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

The description implies when to use this tool through its purpose statement, and it provides guidance on the optional search term: 'If no search term is provided, returns all workflows.' However, it lacks explicit guidance on when to use this tool versus the sibling 'run_workflow' or any alternatives, and it doesn't mention prerequisites or exclusions.

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

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