Skip to main content
Glama

Klinio

Clutch email extractor

clutch_email_extractor

Takes a Clutch directory link (agencies and service firms), lists the companies on it and returns each one'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": {
      "clutch_url": "<clutch_url>"
    },
    "name": "clutch_email_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many companies (1 to 500).
clutch_urlYesA clutch.co directory link, like https://clutch.co/agencies/digital-marketing/united-kingdom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 new information by disclosing the billing model — one credit per company that yields an email or phone. It stops short of explaining what happens with companies that yield nothing, whether the call returns inline or asynchronously, or any rate/limit behavior on the open web.

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 tight sentences with no filler: the first front-loads what goes in and what comes out, the second carries the cost model. Slightly informal verb choice ('Takes') is the only minor weakness.

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 carries the return-value burden and does state that per-company business emails and phones come back. It leaves open the shape of the result set and whether a search is queued rather than resolved, which matters given the get_results/list_searches siblings.

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 both clutch_url and the 1–500 limit are already documented, and baseline 3 applies. The description does not add format, URL-validation, or limit-vs-credit interaction details beyond the schema's own bounds.

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 chain (takes a link, lists companies, returns emails and phones) and pins the resource to a Clutch directory URL, which implicitly separates it from the Google Maps/Google Search/website extractor siblings. It does not explicitly name an alternative, but the source-type constraint makes the tool's identity unambiguous.

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 by the required input being a clutch.co directory link, so an agent can infer this is the path for Clutch-sourced extraction. There is no explicit when-to-use or when-not guidance, and no mention of whether results arrive directly or must be pulled via get_results, despite those siblings existing.

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