Skip to main content
Glama
web-insights-mcp
by nqcthedev

Compare two pages

compare_pages
Read-onlyIdempotent

Fetch two URLs and compare their SEO and content metrics side by side to find content gaps, verify redesign or migration changes, and check landing-page versions.

Instructions

Fetch two URLs and compare them side by side: title, meta description, H1, word count, heading outline (sub-topics covered only by A, only by B, or both), top keywords and two-word phrases, structured-data types and link counts. Use it for competitor content-gap analysis (your page vs. a ranking competitor), before/after checks of a redesign or migration, or comparing two versions of a landing page.

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_a": "<url_a>",
      "url_b": "<url_b>"
    },
    "name": "compare_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_aYesFirst page (e.g. your page).
url_bYesSecond page (e.g. a competitor).
keyword_limitNoHow many top keywords/phrases to compute per page.

Output Schema

NameRequiredDescriptionDefault
aYes
bYes
differencesYes
observationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior (two live fetches, side-by-side diff of specific facets), but says nothing about failure handling when a URL is unreachable, rate/response latency, or how the two pages are aligned. That is acceptable given annotation coverage but not a rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and the compared facets, then the use cases; every clause carries information. The facet list is long but each item is a distinct output dimension, so it earns its space, though the single-sentence enumeration is dense.

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

Completeness4/5

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

With an output schema documenting the return shape, full annotation coverage, and all three parameters documented, the description covers what an agent needs to select and call the tool. The only gap is edge-case behavior around fetch failures or large pages.

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 url_a, url_b, and keyword_limit are already documented including defaults and bounds (keyword_limit 5-50, default 15). The description hints at keyword/phrase output but adds no semantics for the parameters themselves, so the baseline of 3 applies.

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?

States a specific verb+resource (fetch two URLs and compare) and enumerates the exact dimensions compared: title, meta description, H1, word count, heading outline, keywords/phrases, structured-data types, link counts. This clearly separates it from fetch_page, crawl_site, and seo_audit, which operate on a single URL or a whole site.

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

Usage Guidelines4/5

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

Gives three concrete when-to-use scenarios: competitor content-gap analysis, before/after redesign or migration checks, and comparing landing-page versions. It stops short of naming alternatives or stating when not to use it (e.g., single-page fetching, or mass comparison), so it is clear context without explicit routing.

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