Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_map_place

Fetch Google Maps place details by place_id to get name, categories, address, coordinates, phone, website, rating, and review count.

Instructions

Google Maps place details API. Returns the Google Maps details of one place by its Google place_id: name, categories, address, coordinates, phone, website, description, image, amenities, rating and review count. rating is null when the place has no aggregate rating on Google.

Input Schema

NameRequiredDescriptionDefault
place_idYesGoogle Place ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 behavioral burden. It helpfully discloses the exact return fields and the `rating: null` edge case, but says nothing about failure modes for an invalid place_id, rate limits, or auth. It adds real value yet leaves gaps for a network-backed API.

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 sentences, front-loaded with the resource and action, then the field list. Every clause carries information and nothing is wasted.

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 enumerated field list is exactly what the description should provide, and it does so thoroughly. Missing only guidance on how to obtain a place_id and how it relates to the neighboring place_photos / place_reviews tools.

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?

Schema coverage is 100% for the single required `place_id`, so the schema already documents the parameter. The description reinforces that it is a Google place_id rather than some other ID, adding marginal clarity beyond the schema but nothing about sourcing one.

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 ('Returns the Google Maps details of one place by its Google `place_id`') and enumerates the returned fields, so the agent knows exactly what it does. It implicitly contrasts with google_map_search (single known place vs lookup), but never names a sibling to differentiate explicitly.

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

Usage Guidelines3/5

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

Usage is implied: you need a Google place_id, and google_map_place_photos / google_map_place_reviews / google_map_search are obvious alternatives that go unmentioned. No when-to-use or when-not-to-use guidance is given, leaving sibling routing to inference.

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