Skip to main content
Glama
Sign In
ScrapingDog-MCP

ScrapingDog-MCP

by alessandrobenigni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_maps_places

Retrieve complete business profiles from Google Maps, including operating hours, service options, amenities, accessibility features, and payment methods.

Instructions

Retrieves a complete business profile for a specific Google Maps location, including operating hours, service options, amenities, accessibility features, and payment methods. [Credits: Not explicitly stated on this page (see general Scrapingdog credit pricing).] Notes: Two lookup modes: (1) type=place plus data_id, or (2) place_id alone. The docs list type and data_id as Required, but place_id is documented as independently usable without the other optional parameters, effectively making it an alternative required-parameter path. Returns: JSON object (single place) with title, rating, reviews (count), gps_coordinates {latitude, longitude}, type[], address, phone, website, operating_hours (per weekday), service_options {dine_in, takeout, delivery}, amenities {wifi, restroom, seating}, accessibility {wheelchair_accessible_entrance, wheelchair_accessible_seating}, payment_options {credit_cards, debit_cards, nfc_mobile_payments}.

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": {
      "type": "<type>",
      "data_id": "<data_id>"
    },
    "name": "google_maps_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesMust be set to `place` (type=place). Not required when using place_id instead.
countryNoISO country code for the results. See Google Country Parameter documentation for full list. (default: us)
data_idYesThe Google Maps data ID for the location, obtained from the google_maps_search endpoint. Required unless place_id is used instead.
place_idNoUniquely identifies a place on Google Maps; obtainable via the google_maps_search endpoint. Can be used independently without any other optional parameters (i.e., in place of type+data_id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format and fields, but lacks information on error handling, rate limits, authentication, or what happens if no place is found. The credit note is vague.

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?

The description is well-structured with clear sections and front-loaded purpose. The credit note is slightly extraneous, but overall it's efficient and provides necessary detail in a readable format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the number of parameters (4), no output schema, and no annotations, the description is comprehensive. It explains the input parameters' relationships, describes the output fields in detail, and covers the core functionality adequately for an agent to use it correctly.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining the alternative required-parameter paths (type+data_id vs place_id) and clarifying that place_id can be used independently, which goes beyond the schema's field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a complete business profile for a specific Google Maps location, with explicit details on what fields are included. This distinguishes it from sibling tools like google_maps_search (which returns lists) and other specific data tools.

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

Usage Guidelines4/5

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

The description explains two lookup modes (type+data_id vs place_id) and clarifies the parameter requirements. While it doesn't explicitly say when to use this versus alternatives, the context and sibling tool names imply it's for individual place details after a search.

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