Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

google_map_search

Search Google Maps by keyword to retrieve structured place details such as name, address, categories, coordinates, phone, website, rating, and review count.

Instructions

Google Maps search API. Searches Google Maps with a request body of keyword (required) plus optional language (default en) and country (an ISO-2 code such as us, default us). Each place has its name, place id, categories, address, coordinates, phone, website, rating and review count. rating is null when Google has no aggregate rating.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mapSearchOption": "<mapSearchOption>"
    },
    "name": "google_map_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapSearchOptionYesSearch options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / mapSearchOption / properties
      Added value: +{
      +  "country": {
      +    "type": "string"
      +  },
      +  "keyword": {
      +    "type": "string"
      +  },
      +  "language": {
      +    "type": "string"
      +  }
      +}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the whole behavioral burden. It usefully discloses the per-place return fields and the null-rating edge case, which is real value, but it says nothing about result counts, pagination, quota/rate limits, or authentication expectations for a network-backed search.

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

Conciseness4/5

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

Three tight sentences, front-loaded with the resource and then the request-body shape, followed by the output shape. The opening 'Google Maps search API.' is mildly redundant with the tool name but costs little.

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?

With no output schema, the description correctly spends its space enumerating return fields and the null-rating case, and it documents the nested options object. It falls short only on behavioral context (limits, pagination, permissions) that no annotation covers.

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

Parameters4/5

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

The schema's nested object only says 'Search options' and leaves the individual properties undescribed, so the description genuinely adds meaning: keyword is required, language defaults to en, and country is an ISO-2 code defaulting to us. That is more than the structured data conveys, though it does not explain keyword syntax or result limits.

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 gives a specific verb and resource ('Searches Google Maps') and lists the query inputs, so the agent knows exactly what the tool does. It does not, however, distinguish itself from near-identical siblings such as datasets_google_map_search, google_map_nearby or google_map_place, so the agent must guess which one a keyword lookup belongs to.

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?

It states that a keyword is required and gives defaults for language and country, which implies a free-text place lookup. It offers no when-to-use or when-not-to-use guidance and never names an alternative for nearby searches or single-place lookups, which is the main ambiguity for this family of tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools