Skip to main content
Glama
flyanima

Open Search MCP

by flyanima

search_startpage

Search the web privately using Startpage to get Google results without tracking. Filter results by time range, language, and quantity for focused research.

Instructions

Search using Startpage - Google results with privacy protection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for Startpage
maxResultsNoMaximum number of results to return (1-20)
languageNoSearch language (e.g., "en", "de", "fr")en
timeRangeNoTime range filter: any, day, week, month, yearany

Implementation Reference

  • Execute handler for 'search_startpage' tool. Parses input arguments, calls the underlying searchStartpage client method, formats results with timing, metadata, privacy info, and handles errors with suggestions.
    execute: async (args: any) => {
      try {
        const { query, maxResults = 10, language = 'en', timeRange = 'any' } = args;
        
        const startTime = Date.now();
        const result = await client.searchStartpage(query, { maxResults, language, timeRange });
        const searchTime = Date.now() - startTime;
    
        return {
          success: true,
          data: {
            source: 'Startpage',
            query,
            language,
            timeRange,
            totalResults: result.results.length,
            results: result.results,
            searchTime,
            timestamp: Date.now(),
            privacy: result.privacy,
            features: result.features,
            searchMetadata: {
              engine: 'Startpage',
              basedOn: 'Google results',
              tracking: false,
              logging: false
            }
          }
        };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : 'Startpage search failed',
          data: {
            source: 'Startpage',
            query: args.query,
            results: [],
            suggestions: [
              'Try different search terms',
              'Check spelling and grammar',
              'Use more specific keywords'
            ]
          }
        };
      }
  • Core helper method that generates mock search results for Startpage using generateSearchResults, adds privacy metadata, simulates Google proxy without tracking.
    async searchStartpage(query: string, options: any = {}) {
      try {
        // Startpage是Google结果的隐私代理,我们使用模拟数据
        const results = this.generateSearchResults(query, 'Startpage', options.maxResults || 10);
        return {
          success: true,
          results,
          source: 'Startpage',
          privacy: 'Google results without tracking',
          features: ['No IP logging', 'No cookies', 'Anonymous proxy']
        };
      } catch (error) {
        throw new Error(`Startpage search failed: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input schema for search_startpage tool defining query (required), maxResults (1-20), language, and timeRange parameters.
    inputSchema: {
      type: 'object',
      properties: {
        query: {
          type: 'string',
          description: 'Search query for Startpage'
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of results to return (1-20)',
          default: 10,
          minimum: 1,
          maximum: 20
        },
        language: {
          type: 'string',
          description: 'Search language (e.g., "en", "de", "fr")',
          default: 'en'
        },
        timeRange: {
          type: 'string',
          description: 'Time range filter: any, day, week, month, year',
          default: 'any',
          enum: ['any', 'day', 'week', 'month', 'year']
        }
      },
      required: ['query']
    },
  • Tool registration block for 'search_startpage' including name, description, category, source, inputSchema, and execute handler.
    registry.registerTool({
      name: 'search_startpage',
      description: 'Search using Startpage - Google results with privacy protection',
      category: 'search',
      source: 'Startpage',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query for Startpage'
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of results to return (1-20)',
            default: 10,
            minimum: 1,
            maximum: 20
          },
          language: {
            type: 'string',
            description: 'Search language (e.g., "en", "de", "fr")',
            default: 'en'
          },
          timeRange: {
            type: 'string',
            description: 'Time range filter: any, day, week, month, year',
            default: 'any',
            enum: ['any', 'day', 'week', 'month', 'year']
          }
        },
        required: ['query']
      },
      execute: async (args: any) => {
        try {
          const { query, maxResults = 10, language = 'en', timeRange = 'any' } = args;
          
          const startTime = Date.now();
          const result = await client.searchStartpage(query, { maxResults, language, timeRange });
          const searchTime = Date.now() - startTime;
    
          return {
            success: true,
            data: {
              source: 'Startpage',
              query,
              language,
              timeRange,
              totalResults: result.results.length,
              results: result.results,
              searchTime,
              timestamp: Date.now(),
              privacy: result.privacy,
              features: result.features,
              searchMetadata: {
                engine: 'Startpage',
                basedOn: 'Google results',
                tracking: false,
                logging: false
              }
            }
          };
        } catch (error) {
          return {
            success: false,
            error: error instanceof Error ? error.message : 'Startpage search failed',
            data: {
              source: 'Startpage',
              query: args.query,
              results: [],
              suggestions: [
                'Try different search terms',
                'Check spelling and grammar',
                'Use more specific keywords'
              ]
            }
          };
        }
      }
    });
  • src/index.ts:241-241 (registration)
    Top-level call to registerAlternativeSearchEngines which includes the search_startpage tool registration.
    registerAlternativeSearchEngines(this.toolRegistry); // 3 tools: search_startpage, search_brave, search_ecosia
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. While it mentions 'privacy protection' as a key feature, it doesn't describe important behavioral aspects: what format results are returned in, whether there are rate limits, authentication requirements, error conditions, or what happens when no results are found. For a search tool with no annotation coverage, this is a significant gap.

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 extremely concise - a single sentence that efficiently communicates the core functionality. It's front-loaded with the essential information (search with Startpage) and includes the key differentiator (privacy protection). There's zero wasted verbiage or redundancy.

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

Completeness2/5

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

Given the complexity of a search tool with 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (format, structure, fields), doesn't mention error handling or limitations, and provides no context about when this tool is appropriate versus the many other search tools available. For a tool in this context, more completeness is needed.

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 already fully documents all 4 parameters (query, maxResults, language, timeRange) with descriptions, defaults, constraints, and enums. The description adds no parameter-specific information beyond what's in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 using Startpage - Google results with privacy protection'. It specifies the verb ('Search'), resource ('Startpage'), and key differentiator ('Google results with privacy protection'). However, it doesn't explicitly distinguish this tool from its many sibling search tools (e.g., search_arxiv, search_pubmed, search_brave), which would require a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With 28 sibling tools including many other search tools (search_arxiv, search_pubmed, search_brave, search_ecosia, search_searx, etc.), there's no indication of when Startpage is preferred over other search engines or research tools. The description doesn't mention any specific use cases, 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/flyanima/open-search-mcp'

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