Skip to main content
Glama
localseodata

Local SEO Data

Official

maps

Read-only

Retrieve Google Maps listings for any keyword and location, returning names, ratings, reviews, addresses, phone numbers, websites, hours, GPS coordinates, and categories.

Instructions

Get Google Maps results for a keyword and location. Returns names, place IDs, ratings, reviews, addresses, phone numbers, websites, hours, GPS coordinates, and categories. Costs 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesSearch keyword (e.g. "dentist")
locationYesCity and state (e.g. "Orchard Park, NY")
limitNoNumber of results. Default: 20, max: 100

Implementation Reference

  • The handler function for the 'maps' tool. It calls the API at /v1/serp/maps with keyword, location, and optional limit parameters, then formats the result as text content.
      withErrorHandling(async ({ keyword, location, limit }) => {
        const result = await callApi(
          "/v1/serp/maps",
          { keyword, location, ...(limit && { limit }) },
          getAuth()
        );
        return { content: [{ type: "text" as const, text: formatResult(result.data, result) }] };
      })
    );
  • The input schema for the 'maps' tool using Zod: keyword (string), location (string), and optional limit (integer 1-100).
    {
      keyword: z.string().describe('Search keyword (e.g. "dentist")'),
      location: z.string().describe('City and state (e.g. "Orchard Park, NY")'),
      limit: z.number().int().min(1).max(100).optional().describe("Number of results. Default: 20, max: 100"),
    },
  • The registration of the 'maps' tool via server.tool() inside registerSerpTools(), which is called from server.ts (line 35).
    server.tool(
      "maps",
      "Get Google Maps results for a keyword and location. Returns names, place IDs, ratings, reviews, addresses, phone numbers, websites, hours, GPS coordinates, and categories. Costs 1 credit.",
      {
        keyword: z.string().describe('Search keyword (e.g. "dentist")'),
        location: z.string().describe('City and state (e.g. "Orchard Park, NY")'),
        limit: z.number().int().min(1).max(100).optional().describe("Number of results. Default: 20, max: 100"),
      },
      READ_ONLY,
      withErrorHandling(async ({ keyword, location, limit }) => {
        const result = await callApi(
          "/v1/serp/maps",
          { keyword, location, ...(limit && { limit }) },
          getAuth()
        );
        return { content: [{ type: "text" as const, text: formatResult(result.data, result) }] };
      })
    );
  • src/server.ts:35-35 (registration)
    The call to registerSerpTools(server, getAuth) in createMcpServer() which registers the 'maps' tool (among other SERP tools).
    registerSerpTools(server, getAuth);
Behavior4/5

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

The description discloses the credit cost and lists returned data fields, adding value beyond the annotations which already indicate non-destructive read-only behavior. No contradictions.

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?

Two concise sentences cover purpose, outputs, and cost with no wasted words. Front-loaded with the core action.

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 no output schema, the description adequately explains return values. It could mention result limitations or sorting, but is sufficient for a simple search tool.

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?

With 100% schema description coverage, the schema already explains parameters. The description adds context about return fields and cost, but does not enhance parameter meaning further.

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 it retrieves Google Maps results for a keyword and location, listing specific return fields. While it doesn't explicitly differentiate from siblings like local_finder or local_pack, the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternative tools for similar queries, nor any scenarios where it should be avoided.

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

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