Skip to main content
Glama

Extract contact details from a web page

contacts
Read-only

Extract contact details from a web page: email addresses (including mailto links and [at]-obfuscated ones), phone numbers (tel links and visible numbers) and postal addresses from structured data. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's real contribution is the operational context: expected latency of 1-3 s, a 20 calls/day free quota per user, and a $0.003 per-call x402/USDC-on-Base charge above that. It also discloses which obfuscation forms are handled, which matters for trusting results, though it says nothing about behavior on pages with no contacts or about partial/failed extraction.

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 short sentences, front-loaded with purpose before cost. The latency and pricing clauses are dense but each carries decision-relevant information an agent needs before calling a metered endpoint; nothing is filler.

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 only two parameters, full schema coverage, and no output schema, the description covers what an agent needs: what is extracted, how long it takes, and how the payment handshake works. The main residual gap is the shape of the response (per-field lists, counts, or empty-result behavior), which is not documented anywhere since there is no output schema.

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 parameters are already documented, including the payment signature flow. The description adds no meaning beyond the schema for either the url or the payment parameter, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Extract contact details from a web page') and then enumerates exactly what counts as contact details: emails including mailto and [at]-obfuscated forms, phones including tel links, and postal addresses from structured data. That enumeration distinguishes it from siblings like links, page_text, and page_markdown, which would return raw content rather than parsed contact entities.

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?

The scope statement implies when to reach for this tool (you want contact info from a URL), and the pricing/payment sentences give clear operational context for the paid path. However, it never names an alternative or states when not to use it, so the agent must infer selection against the other 30+ siblings on its own.

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.