Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_map_search

Search Google Maps by keyword, language, and country to retrieve structured place details including name, address, coordinates, phone, website, rating, and reviews.

Instructions

Google Maps search API. Searches Google Maps with a request body of keyword, language and country (an ISO-2 code such as us), all required. 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.

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?

With no annotations, the description carries the full burden; it usefully discloses the returned place shape and the notable edge case that rating is null when Google has no aggregate rating. It says nothing about rate limits, pagination, result counts, auth, or cost, which for a search endpoint is a meaningful gap.

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 sentences, front-loaded with the operation, then inputs, then output shape and the null-rating caveat. No filler; each sentence carries information, though the output-field list is a mild enumeration dump.

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 does the work of describing the returned fields, and it covers the required nested inputs. What remains missing is behavioral context (paging, limits, count of results) and any routing guidance among the many map/location siblings.

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 documents only the wrapper object ('Search options') and leaves the nested fields bare, so the description meaningfully compensates: it names keyword, language and country, marks all as required, and specifies that country is an ISO-2 code like 'us'. That format detail is absent from the schema and adds real value.

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?

States a specific verb and resource ('Searches Google Maps') and names the required request fields, so the agent knows this is a keyword search returning place records. It does not, however, distinguish itself from close siblings such as google_map_place or datasets_google_map_search, so an agent must infer which to pick.

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?

There is no when-to-use statement, no mention of alternatives (e.g. google_map_place for a single place, geocoding tools for addresses), and no prerequisites or exclusions. The description only enumerates inputs and outputs.

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