Skip to main content
Glama

BRAINIAC Web & Page Intelligence

Extract website metadata

web-intelligence_website-metadata-extract
Read-onlyIdempotent

Read title, description, canonical URL, Open Graph tags, language, and robots directives from one public page. Absent tags are null. robots.txt is not fetched. Price $0.02 USDC. POST /api/v1/web-intelligence/website-metadata-extract. An unpaid call returns the x402 payment terms and does not run.

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": "web-intelligence_website-metadata-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesurl, string, length 8 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
titleNotitle. String.
robotsNorobots. Object.
sourcesNosources. Array.
finalUrlNofinalUrl. String.
languageNolanguage. String.
warningsNowarnings. Array.
openGraphNoopenGraph. Object.
httpStatusNohttpStatus. Number.
contentTypeNocontentType. String.
descriptionNodescription. String.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
canonicalUrlNocanonicalUrl. String.
requestedUrlNorequestedUrl. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive/openWorld), the description discloses pricing ($0.02 USDC), the transport endpoint, and the failure mode that an unpaid call returns x402 payment terms without executing. It also clarifies that absent tags are returned as null rather than omitted, which is behavior the schema cannot express.

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?

Four short sentences, each earning its place: capability list first, null semantics second, scope exclusion third, then commercial and endpoint detail. Nothing is repeated from the annotations and the most decision-relevant information is front-loaded.

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 present, the description need not explain return values, and it correctly covers pricing, payment gating, and null handling. The remaining gap is edge-case behavior such as JavaScript rendering, redirects, or error responses for unreachable pages, which an agent calling this tool might still wonder about.

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% for the single url parameter, so the baseline is 3. The description adds only the qualifier "one public page," which hints at the URL's expected nature but does not elaborate on format, redirects, or what counts as public beyond the schema's regex pattern.

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?

The description opens with a specific verb ("Read") and enumerates the exact resource fields returned: title, description, canonical URL, Open Graph tags, language, robots directives from one public page. That is far more precise than the tool name alone. It does not explicitly contrast itself with siblings such as url-to-markdown or structured-page-extract, so it lands just short of a 5.

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

Usage Guidelines3/5

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

Scope limits act as implicit usage guidance: "one public page" and "robots.txt is not fetched" tell the agent what this tool will not do. However, there is no explicit statement of when to choose it over the metadata-adjacent siblings, so the agent must infer the routing from the field list.

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.

Resources