webdatatools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your personal Apify API token. Tool discovery works without it, but calling a tool without it returns a friendly error telling you where to get one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web and get back clean Markdown of the top results (or read specific URLs directly, skipping search). Good default choice for 'what is X' / 'find info about X' questions. Each result page fetched is a billed row. |
| read_urlA | Fetch one or more article/blog/news URLs and return clean, readable article text as Markdown (title, author, date, body). Use this instead of web_search when you already have the exact URL to read. |
| crawl_site_markdownA | Crawl a website starting from one URL and return one Markdown document per page (docs sites, blogs, knowledge bases). Billed per page crawled, so keep |
| extract_contactsB | Crawl a website's home/about/contact pages and pull out e-mail addresses, phone numbers and social profile links (LinkedIn, X/Twitter, Instagram, Facebook, YouTube, TikTok, GitHub, Telegram, WhatsApp). |
| detect_tech_stackB | Fingerprint a website's technology stack: CMS, e-commerce platform, analytics, ad pixels, e-mail marketing, chat widgets, payment providers, front-end frameworks, cookie consent, CDN/hosting and web server. |
| company_profileA | Build a one-stop company profile for a domain: contacts, tech stack, DNS/e-mail security, TLS/security grade, hiring signals, Wikidata company facts (HQ, employees, revenue, founders) and an SEO audit. Turn off sections you don't need to make the run cheaper and faster. |
| check_email_securityB | Check a domain's DNS and e-mail security posture: SPF, DMARC, DKIM selector presence, mail/DNS provider, registrar and domain age, with an overall 0-100 score. |
| validate_emailsA | Validate a list of e-mail addresses: syntax check, disposable/role-account detection and (optionally) a live MX/A DNS lookup to confirm the domain can receive mail. Good for cleaning a lead list before sending. |
| package_healthA | Check the health of npm, PyPI or Crates.io packages: latest version, publish recency, download stats, license, and (optionally) GitHub stars/forks/open-issues/archived status. Prefix a name with its registry, e.g. pypi:requests. |
| google_searchA | Run a raw Google search and get back structured SERP data: organic results, People Also Ask, related searches. Use this when you need Google's ranking/position data itself, not just page content (for that, use web_search). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
web_search and google_search are distinct (page content vs SERP rankings), but web_search can also read URLs directly, overlapping with read_url. company_profile bundles check_email_security, detect_tech_stack, and extract_contacts, so an agent must decide between the aggregate and individual tools.
All names use snake_case, but the pattern is mixed: most are verb_noun (check_email_security, validate_emails, read_url, extract_contacts, detect_tech_stack, crawl_site_markdown) while several are noun_noun (web_search, google_search, company_profile, package_health). Still readable and consistent in casing.
10 tools is well within the 3–15 sweet spot for a web data toolkit, and each covers a distinct capability (search, crawl, extract, validate, profile). No obvious redundancy despite company_profile bundling others.
Covers search, URL reading, crawling, contact extraction, tech detection, email security/validation, company profiling, package health, and SERP data. Minor gaps exist (e.g., structured data extraction, sitemap parsing, or a dedicated TLS check), but core web-research workflows are fully supported.