Skip to main content
Glama

Klinio

Google Maps email extractor

google_maps_email_extractor

Finds the businesses on Google Maps for a kind of business in a place (for example query "dentists", location "Berlin"), visits each one's website and returns its business emails and phones. Send query with location, or maps_url (a Google Maps search link). Spends one credit per company with an email or phone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "google_maps_email_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many companies (1 to 500).
queryNoWhat to look for: a kind of business, like "dentists" or "web design agencies".
locationNoWhere: a city, district, region or country, like "Kadıköy, İstanbul" or "Austin, TX".
maps_urlNoInstead of query and location: a Google Maps search link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses real behavior: it crawls each business's website, returns both emails and phones, and bills "one credit per company with an email or phone" – a cost model the agent cannot infer from structured fields. It omits whether the call blocks until results return or enqueues a job, which matters given the list_searches/get_results/stop_search siblings.

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?

Three sentences, front-loaded with what the tool does, then the input contract, then the cost. Every sentence carries distinct information with no repetition of schema text.

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 states the return content (business emails and phones), and the billing note covers the main cost risk for an open-world scraping tool. The remaining gap is execution semantics – synchronous response versus a search job tracked by the sibling tools – which an agent needs to know before calling.

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 description coverage is 100%, so the schema already documents all four parameters, and the baseline of 3 applies. The description does add the useful constraint that maps_url replaces query+location rather than combining with them, but adds no format or range detail beyond the schema.

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 uses a concrete verb+resource ("finds the businesses on Google Maps... visits each one's website and returns its business emails and phones") and anchors it with worked examples ("dentists", "Berlin"). The Google Maps source implicitly separates it from the clutch and website-level siblings, but no sibling is named explicitly.

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?

"Send query with location, or maps_url" explicitly resolves the two valid input modes and marks maps_url as the substitute for the query/location pair, which prevents malformed calls on a zero-required-parameter schema. It does not say when to prefer this tool over website_email_finder or clutch_email_extractor for the same research goal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources