mcp-server-scraper

extract_metadata

Extract structured metadata from web pages including titles, descriptions, Open Graph tags, canonical URLs, and favicons for content analysis and SEO optimization.

Instructions

Extract page metadata: title, description, Open Graph tags (og:title, og:description, og:image), canonical URL, and favicon.

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": "extract_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to extract metadata from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states what metadata is extracted but doesn't disclose behavioral traits such as error handling, rate limits, authentication needs, or what happens if metadata is missing. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the purpose and lists specific metadata types. There is zero waste, and every word earns its place.

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

Completeness3/5

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

Given no annotations, no output schema, and a simple input schema, the description is adequate for a basic extraction tool but lacks completeness. It doesn't explain return values, error cases, or behavioral context, which are needed for full understanding.

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 description coverage is 100%, so the schema already documents the 'url' parameter. The description adds no additional parameter semantics beyond what the schema provides, such as URL format expectations or examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb 'extract' and the resource 'page metadata', with specific examples of what metadata is extracted (title, description, Open Graph tags, canonical URL, favicon). It distinguishes from sibling tools like 'extract_links' by focusing on metadata rather than links.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'scrape_url' or 'search_page'. The description implies usage for extracting metadata from a URL but doesn't specify scenarios, prerequisites, or exclusions.

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

Deploy Server