Skip to main content
Glama
lianshuang-photo

SearchAPI MCP Server

search_google_videos

Search Google Videos to find video content across the web using customizable filters for location, language, time period, and safety settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes搜索查询
deviceNo设备类型desktop
locationNo位置
uuleNo位置编码
google_domainNoGoogle域名google.com
glNo地理位置us
hlNo语言en
lrNo语言限制
crNo国家限制
nfprNo不进行拼写检查0
filterNo过滤结果1
safeNo安全搜索off
time_periodNo时间段
time_period_minNo最小时间段
time_period_maxNo最大时间段
numNo结果数量10
pageNo页码1

Implementation Reference

  • src/index.js:623-668 (registration)
    Registration of the 'search_google_videos' MCP tool using server.tool(), including inline schema and handler function.
    server.tool(
      'search_google_videos',
      {
        q: z.string().describe('搜索查询'),
        device: z.string().default('desktop').describe('设备类型'),
        location: z.string().optional().describe('位置'),
        uule: z.string().optional().describe('位置编码'),
        google_domain: z.string().default('google.com').describe('Google域名'),
        gl: z.string().default('us').describe('地理位置'),
        hl: z.string().default('en').describe('语言'),
        lr: z.string().optional().describe('语言限制'),
        cr: z.string().optional().describe('国家限制'),
        nfpr: z.string().default('0').describe('不进行拼写检查'),
        filter: z.string().default('1').describe('过滤结果'),
        safe: z.string().default('off').describe('安全搜索'),
        time_period: z.string().optional().describe('时间段'),
        time_period_min: z.string().optional().describe('最小时间段'),
        time_period_max: z.string().optional().describe('最大时间段'),
        num: z.string().default('10').describe('结果数量'),
        page: z.string().default('1').describe('页码')
      },
      async (args) => {
        const params = {
          engine: 'google_videos',
          q: args.q
        };
        
        // 添加可选参数
        const optionalParams = [
          'device', 'location', 'uule', 'google_domain', 'gl', 'hl', 'lr', 'cr',
          'nfpr', 'filter', 'safe', 'time_period', 'time_period_min', 'time_period_max',
          'num', 'page'
        ];
        
        for (const key of optionalParams) {
          if (args[key] !== undefined) {
            params[key] = args[key];
          }
        }
        
        const result = await makeSearchapiRequest(params);
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
        };
      }
    );
  • Handler function that prepares search parameters for Google Videos engine using searchapi.io API and returns JSON-formatted results.
    async (args) => {
      const params = {
        engine: 'google_videos',
        q: args.q
      };
      
      // 添加可选参数
      const optionalParams = [
        'device', 'location', 'uule', 'google_domain', 'gl', 'hl', 'lr', 'cr',
        'nfpr', 'filter', 'safe', 'time_period', 'time_period_min', 'time_period_max',
        'num', 'page'
      ];
      
      for (const key of optionalParams) {
        if (args[key] !== undefined) {
          params[key] = args[key];
        }
      }
      
      const result = await makeSearchapiRequest(params);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
      };
    }
  • Zod-based input schema defining parameters for Google Videos search, including query and various optional filters.
    {
      q: z.string().describe('搜索查询'),
      device: z.string().default('desktop').describe('设备类型'),
      location: z.string().optional().describe('位置'),
      uule: z.string().optional().describe('位置编码'),
      google_domain: z.string().default('google.com').describe('Google域名'),
      gl: z.string().default('us').describe('地理位置'),
      hl: z.string().default('en').describe('语言'),
      lr: z.string().optional().describe('语言限制'),
      cr: z.string().optional().describe('国家限制'),
      nfpr: z.string().default('0').describe('不进行拼写检查'),
      filter: z.string().default('1').describe('过滤结果'),
      safe: z.string().default('off').describe('安全搜索'),
      time_period: z.string().optional().describe('时间段'),
      time_period_min: z.string().optional().describe('最小时间段'),
      time_period_max: z.string().optional().describe('最大时间段'),
      num: z.string().default('10').describe('结果数量'),
      page: z.string().default('1').describe('页码')
  • Shared utility function to make HTTP requests to searchapi.io API, handles errors and adds API key; used by search_google_videos tool.
    async function makeSearchapiRequest(params) {
      // 确保API Key被添加到参数中
      params.api_key = SEARCHAPI_API_KEY;
      
      try {
        const response = await axios.get(SEARCHAPI_URL, {
          params,
          timeout: 30000 // 30秒超时
        });
        return response.data;
      } catch (error) {
        let errorDetail = null;
        
        if (error.response) {
          try {
            errorDetail = error.response.data;
          } catch (e) {
            errorDetail = error.response.statusText;
          }
        }
        
        const errorMessage = `调用searchapi.io时出错: ${error.message}`;
        if (errorDetail) {
          return { error: `${errorMessage}, 详情: ${JSON.stringify(errorDetail)}` };
        }
        
        return { error: errorMessage };
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/lianshuang-photo/searchapi-mcp-nodejs'

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