Skip to main content
Glama

Klinio

Google search email extractor

google_search_email_extractor

Takes the link of a Google search (from the All or Web tab), lists the company websites it finds and returns each company's business emails and phones. Spends one credit per company with an email or phone.

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": {
      "search_url": "<search_url>"
    },
    "name": "google_search_email_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many companies (1 to 500).
countryNoTwo letters (like "tr" or "gb"): the country to run a google.com search from.
search_urlYesA google.com search link, like https://www.google.com/search?q=web+design+agency+ankara

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations only declare readOnlyHint=false and openWorldHint=true; the description adds genuinely useful non-schema context in 'Spends one credit per company with an email or phone', which tells the agent this is a billable, result-dependent write against account credits. However, it omits execution-model details an agent likely needs (whether results are returned synchronously or via a search/job id given the presence of get_results-style siblings), and does not say what happens when a site yields no email or phone, other than implying no charge.

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?

Two compact sentences with zero filler: the first defines input, intermediate step, and output in one pass, and the second delivers the cost rule. Slight density cost in the long first sentence, but nothing is redundant or misplaced.

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

Completeness3/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 carries the burden of describing returns and does so only at a high level ('emails and phones' per company, plus a listed set of websites). For an open-world, credit-consuming extraction tool, missing pieces are the response shape/pagination and whether follow-up calls are required to retrieve results, leaving the definition adequate but not fully self-sufficient.

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 all three parameters (search_url, limit, country) are already documented and a baseline of 3 applies. The description adds one piece of meaning beyond the schema by tying company count to cost ('one credit per company'), which lets the agent reason that limit drives spend, but it says nothing about the country parameter's effect or the 1-500 limit range.

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 states a specific input ('the link of a Google search from the All or Web tab') and a specific output ('each company's business emails and phones'), with the intermediate step ('lists the company websites it finds') made explicit. The Google-Search-scoped resource implicitly separates it from google_maps_email_extractor and clutch_email_extractor, but no sibling is named or contrasted directly.

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 context is implied by the required input type: you should call this when you already hold a google.com search URL from the All or Web tab. There is no explicit when-not guidance, no mention of what to do with Maps or directory sources instead, and no statement of prerequisites such as an authenticated/credited account.

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