Skip to main content
Glama
ToolTrace-io

ToolTrace MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TOOLTRACE_API_KEYYesYour ToolTrace API key. Sign up at tooltrace.io/signup to get a free key.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
tooltrace_extractA

Extract clean content from a webpage. Returns Markdown, plain text, metadata, links, JSON-LD schema, and content sections. Use this for scraping, RAG ingestion, or content analysis.

tooltrace_metadataA

Extract page metadata: title, description, canonical URL, author, publication date, favicon, Open Graph, and Twitter card fields. Lightweight alternative to full extraction.

tooltrace_linksB

Extract all links from a webpage with anchor text, internal/external classification, and normalized URLs.

tooltrace_schemaA

Extract JSON-LD structured data from a webpage. Returns schema.org entities like Article, Product, Organization, FAQ, BreadcrumbList, etc.

tooltrace_seo_auditA

Run an SEO audit on a webpage. Returns a score (0-100), weighted checks for metadata, headings, images, canonical signals, robots directives, social tags, schema, and content length, with evidence and recommendations.

tooltrace_tech_stackB

Detect the technology stack of a website: CMS, frameworks, JavaScript libraries, analytics, CDN, hosting, fonts, security tools, and more. Returns categorized detections with confidence levels.

tooltrace_sitemapA

Inspect a website's sitemap. Discovers sitemap URLs, parses sitemap XML, and returns listed page URLs with last-modified dates and change frequencies.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct website analysis concern (sitemap, content, metadata, links, schema, SEO audit, tech stack), and descriptions clarify specialized use cases. The main ambiguity is that tooltrace_extract includes metadata, links, and schema, potentially overlapping with the dedicated extraction tools, but explicit 'lightweight' and 'specific' intent reduces confusion.

Naming Consistency5/5

All tools follow a consistent 'tooltrace_<feature>' pattern using snake_case, making the naming predictable and uniform. Although one tool uses a verb (extract) while others use nouns, the pattern is consistent and no mixing of conventions exists.

Tool Count5/5

Seven tools is well within the ideal 3-15 range for a website analysis server. Each tool serves a distinct, useful function without redundancy or unnecessary bloat.

Completeness4/5

The server covers the core website analysis workflow: discovery (sitemap), content extraction, metadata, links, structured data, SEO auditing, and tech stack detection. Minor gaps like a dedicated robots.txt checker or performance metrics are absent, but agents can accomplish primary tasks without significant workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo issues