Skip to main content
Glama
sparrow84001

SEO, AEO, GEO & Digital Marketing Audit + Safe Fix MCP Server

by sparrow84001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_crawl_and_extract

Crawl a live URL or parse a local HTML file to extract SEO metadata: title, meta description, headings, canonical, JSON-LD, OpenGraph/Twitter, links, and images. Use for single-page audits.

Instructions

Crawls a live URL via HTTP or parses a local HTML/template file to extract raw SEO metadata: Title, Meta Description, Headings (H1-H6), Canonical URL, JSON-LD Schemas, OpenGraph/Twitter cards, links, and images.

USAGE GUIDELINES:

  • Use to extract structured page metadata before running specialized audits or when analyzing a single page.

  • Do NOT use for multi-page batch crawling; use 'seo_audit_sitemap_multipage' instead.

  • Do NOT use to discover framework architecture; use 'seo_discover_project' instead.

BEHAVIORAL TRANSPARENCY:

  • Read-only data extraction.

  • Issues HTTP GET requests for live URLs. Reads local files directly without modifying them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget live URL (e.g. "https://example.com") or local source/HTML file path (e.g. "./index.html").
pageTypeNoOptional override for page classification (e.g. "homepage", "service", "product", "blog", "location"). Inferred automatically if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / pageType / description
      Previous value: -"Optional override for page type (homepage, service, product, blog, location, etc.)."New value: +"Optional override for page classification (e.g. \"homepage\", \"service\", \"product\", \"blog\", \"location\"). Inferred automatically if omitted."
    • changedInput schema / properties / target / description
      Previous value: -"Target live URL (https://...) or local file path."New value: +"Target live URL (e.g. \"https://example.com\") or local source/HTML file path (e.g. \"./index.html\")."
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

The description explicitly states it is read-only, issues HTTP GET requests for live URLs, and reads local files without modifying them. Since no annotations were provided, this transparency fully covers the behavioral contract and sets accurate expectations for side effects.

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?

The description is concise and well-organized: a main action sentence followed by bulleted usage and behavior notes. Every sentence adds value—no filler or redundancy. The most important information (what it does) is front-loaded.

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?

Given the absence of an output schema, the description compensates by listing the extracted metadata fields. It also covers usage boundaries and behavioral details, making the tool's capabilities fully understandable for an agent without needing to inspect additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are described with concrete examples and clarifications. The 'target' parameter explains it can be a URL or file path with format examples; 'pageType' explains it is an optional override with example values and notes that inference occurs when omitted. This adds meaning beyond the raw schema types.

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 clearly states the tool crawls a live URL via HTTP or parses a local HTML/template file to extract raw SEO metadata, listing specific data points (title, meta description, headings, etc.). It explicitly differentiates from sibling tools by noting that multi-page crawling and framework discovery are handled by other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit when-to-use guidance ('before running specialized audits or when analyzing a single page') and when-not-to-use guidance with named alternatives ('Do NOT use for multi-page batch crawling; use seo_audit_sitemap_multipage' and 'Do NOT use to discover framework architecture; use seo_discover_project'). This leaves no ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools