Haunt API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HAUNT_API_KEY | Yes |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_urlA | Extract structured data from any web page by providing a URL and describing what you want. Returns clean JSON with exactly the fields you asked for — no HTML parsing needed. Handles JavaScript-rendered pages and Cloudflare-protected sites automatically. This is the general-purpose extraction tool. Use extract_article for full article content or extract_metadata for page meta tags — they are optimised shortcuts. Read-only — makes no changes to any external system. Requires HAUNT_API_KEY environment variable. Free tier: 100 requests/month. Returns an error if rate limit or API key is invalid. |
| extract_articleA | Extract the main article content from a news article or blog post. Returns title, body text, author, and publish date as structured JSON. Handles paywalled and JavaScript-rendered articles. Optimised for editorial content — use extract_url for product pages, listings, or generic data. Read-only — makes no changes to any external system. Requires HAUNT_API_KEY environment variable. Free tier: 100 requests/month. Returns an error if rate limit or API key is invalid. |
| extract_metadataA | Pull metadata from any URL: title, description, Open Graph tags, Twitter cards, canonical URL. Returns structured JSON with all available meta information. Useful for link previews, SEO analysis, and content categorisation. Use extract_url for page body content or extract_article for full articles. Read-only — makes no changes to any external system. Requires HAUNT_API_KEY environment variable. Free tier: 100 requests/month. Returns an error if rate limit or API key is invalid. |
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 3 tools
The tools have overlapping purposes, as all three extract data from URLs, with extract_url described as a general-purpose tool that can handle what the other two do. However, the descriptions clearly differentiate their optimised use cases: extract_article for editorial content, extract_metadata for meta tags, and extract_url for custom extractions, which helps reduce confusion but still leaves some ambiguity.
All tool names follow a consistent verb_noun pattern with 'extract_' as the prefix, using snake_case uniformly. This predictability makes it easy for agents to understand the naming convention and relate the tools to their shared purpose of extraction.
With 3 tools, the count is reasonable for a focused extraction server, but it feels slightly thin as it only covers read-only extraction operations without broader management or configuration tools. The tools are well-scoped within their domain, but the set could benefit from additional complementary functions.
The server covers core extraction tasks for URLs, articles, and metadata, but there are notable gaps such as no update, delete, or management operations (e.g., for API keys or usage tracking). As a read-only extraction service, it lacks lifecycle coverage, which limits agent workflows to just data retrieval without any control or monitoring capabilities.