Skip to main content
Glama
lianshuang-photo

SearchAPI MCP Server

search_google_maps

Search Google Maps for places and businesses using text queries and optional location coordinates to find relevant results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes搜索查询
location_llNo位置坐标,格式为"纬度,经度"

Implementation Reference

  • The handler function for the 'search_google_maps' tool. It constructs the API parameters (engine: 'google_maps', q: query, optional ll: location_ll), calls the makeSearchapiRequest helper, and returns the JSON-formatted result as text content.
    async ({ query, location_ll }) => {
      const params = {
        engine: 'google_maps',
        q: query
      };
      
      if (location_ll) {
        params.ll = location_ll;
      }
      
      const result = await makeSearchapiRequest(params);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
      };
    }
  • Zod input schema for the tool: 'query' (string, required, search query), 'location_ll' (string, optional, location coordinates in 'lat,lng' format).
    {
      query: z.string().describe('搜索查询'),
      location_ll: z.string().optional().describe('位置坐标,格式为"纬度,经度"')
    },
  • src/index.js:60-81 (registration)
    Registration of the 'search_google_maps' tool via server.tool(), specifying the name, input schema, and inline handler function.
    server.tool(
      'search_google_maps',
      {
        query: z.string().describe('搜索查询'),
        location_ll: z.string().optional().describe('位置坐标,格式为"纬度,经度"')
      },
      async ({ query, location_ll }) => {
        const params = {
          engine: 'google_maps',
          q: query
        };
        
        if (location_ll) {
          params.ll = location_ll;
        }
        
        const result = await makeSearchapiRequest(params);
        return {
          content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
        };
      }
    );
  • Shared helper function 'makeSearchapiRequest' that adds the API key, makes GET request to searchapi.io, handles errors, and returns the data or error object. Used by 'search_google_maps' and other tools.
    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