Skip to main content
Glama

inspect_webpage

Structured webpage and site intelligence and SEO inspection tool for any public URL. Extracts comprehensive metadata, OpenGraph, Twitter cards, JSON-LD schemas, contact details (emails, phones, social links), tech stack detection, security headers, and document outline.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL of a webpage to inspect.
deepNoSub-crawl /contact, /about, /pricing and gather DoH/RDAP domain intel.
render_modeNoRendering strategy: 'auto' (HTTP with browser escalation on SPA shell), 'http_only', or 'browser'.auto
force_browserNoForce browser rendering bypassing HTTP tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / deep
      Added value: +{
      +  "default": true,
      +  "description": "Sub-crawl /contact, /about, /pricing and gather DoH/RDAP domain intel.",
      +  "title": "Deep",
      +  "type": "boolean"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the returned content categories, which is genuinely useful. However, it says nothing about failure modes for blocked/bot-protected sites, latency or cost of the sub-crawl, robots/terms considerations, or whether the tool is strictly read-only — all material for an agent deciding to call it.

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?

Two sentences, front-loaded with purpose, then a dense but scannable inventory of outputs. Slightly list-heavy but every item is a concrete capability, so nothing is wasted.

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?

No output schema exists, so the description is right to enumerate return categories, and it does so well. But with no annotations and a multi-mode, sub-crawling tool, the absence of any behavioral or routing guidance leaves the definition adequate rather than complete.

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 coverage is 100%, so the schema already documents url, deep, render_mode, and force_browser thoroughly. The description adds no parameter-level meaning at all — notably it never mentions the sub-crawl of /contact, /about, /pricing or browser escalation, which are the operationally significant switches. Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('inspect') and resource ('any public URL') and enumerates concrete outputs (metadata, OpenGraph, JSON-LD, contact details, tech stack, security headers, document outline). That output inventory distinguishes it in spirit from siblings like extract_webpage_text or screenshot_webpage, but no sibling is named, so the differentiation is left to inference.

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?

The only scope guidance is 'for any public URL'. There is no statement of when to prefer this over fetch_webpage, extract_webpage_text, or map_website, and no when-not conditions (e.g. 'use this when you need SEO/metadata, not raw text'). The agent must guess the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.