Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Extract website contacts

web-intelligence_website-contact-extract
Read-onlyIdempotent

Read publicly displayed emails, tel: links, address elements, and structured contact data from one public page. Linked pages are not crawled, and missing contacts are not guessed. Price $0.04 USDC. POST /api/v1/web-intelligence/website-contact-extract. An unpaid call returns the x402 payment terms and does not run.

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": "web-intelligence_website-contact-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl, string, length 8 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
emailsNoemails. Array.
phonesNophones. Array.
sourcesNosources. Array.
finalUrlNofinalUrl. String.
warningsNowarnings. Array.
addressesNoaddresses. Array.
httpStatusNohttpStatus. Number.
contentTypeNocontentType. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
requestedUrlNorequestedUrl. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description still adds substantial non-obvious behavior: the $0.04 USDC price, the POST transport path, and critically that an unpaid call returns x402 payment terms and does not execute. That last point is exactly the kind of failure-mode context an agent cannot infer from structured fields.

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?

The extraction scope is front-loaded in the first sentence, followed by limits and then billing/transport facts, with no filler. The bare 'POST /api/v1/...' line is marginally redundant with the tool name but does confirm the transport, so it largely earns its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, output-schema-backed tool, the description covers everything an agent needs to decide and invoke correctly: scope, what is not crawled or guessed, cost, and payment-gate failure behavior. Return-value shape is correctly left to the 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 coverage is 100% on the single required `url` parameter, so the schema already carries the pattern, length, and required constraint. The description adds only the indirect implication that the URL must resolve to a single page via 'from one public page'; no format or syntax guidance beyond that. Baseline 3 is appropriate.

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?

States a specific verb (Read) and enumerates the exact resource types extracted (publicly displayed emails, tel: links, address elements, structured contact data) scoped to 'one public page'. This clearly separates it from siblings like website-metadata-extract and url-to-markdown without needing to open either schema.

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?

The clause 'Linked pages are not crawled, and missing contacts are not guessed' defines the boundary conditions an agent needs before choosing this tool over a crawler-style sibling, and gives clear context on what it will not return. It stops short of naming a specific alternative for multi-page crawling, so it is clear but not fully routing.

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