Skip to main content
Glama

Klinio

Website email finder

website_email_finder

Visits company websites (one, or up to 200) 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": {
      "websites": "<websites>"
    },
    "name": "website_email_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
websitesYesCompany websites, like "acme.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the credit disclosure is genuinely additive: one credit is charged per company that yields an email or phone, which implies no charge when nothing is found. It does not cover failure handling, partial results, or rate limits, which limits it below a 5.

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, no waste, with the scope (one or up to 200) and the cost model both front-loaded where an agent will see them before deciding to call.

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?

For a single-parameter scraping tool with no output schema, the description covers input scope, what is returned, and billing. What it omits is the shape of the return payload and behavior on inaccessible or dead sites, which an agent would need for realistic planning.

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% and the single parameter already documents the expected domain format with an example, so the description adds little beyond the schema. The 1-200 bound is stated in prose but is also encoded as minItems/maxItems.

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: it visits company websites and returns business emails and phones, with an explicit 1-200 size scope. The 'website' input distinguishes it implicitly from the clutch/google_maps/google_search extractors, but the description never names those alternatives to confirm the boundary.

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 only implied: it applies when you already have company domains to crawl. There is no explicit when-to-use vs. when-not, no statement about how this differs from the google_search or clutch extractors, and no prerequisites called out.

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