Skip to main content
Glama

Read a page's SEO and sharing metadata, with issues

meta
Read-only

SEO and sharing metadata of one web page, read from its HTML without JavaScript: final URL and status, title and description with their lengths, canonical, robots meta, lang, hreflang, Open Graph and Twitter card tags, JSON-LD types and objects, favicon, heading outline, word count, and an issues list of plain sentences. robots.txt is respected. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL or domain, e.g. example.com

Output Schema

NameRequiredDescriptionDefault
urlNo
langNo
iconsNo
titleNo
issuesNo
jsonLdNo
robotsNo
statusNo
twitterNo
finalUrlNo
headingsNo
hreflangNo
canonicalNo
checkedAtNo
openGraphNo
wordCountNo
contentTypeNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "canonical": {},
      +    "checkedAt": {},
      +    "contentType": {},
      +    "description": {},
      +    "finalUrl": {},
      +    "headings": {},
      +    "hreflang": {},
      +    "icons": {},
      +    "issues": {},
      +    "jsonLd": {},
      +    "lang": {},
      +    "openGraph": {},
      +    "robots": {},
      +    "status": {},
      +    "title": {},
      +    "twitter": {},
      +    "url": {},
      +    "wordCount": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world, but the description adds material context beyond them: no JavaScript execution, robots.txt compliance, a per-call price of $0.002 via x402 with failed calls free. That cost and fetching-model disclosure is exactly what an agent needs before calling. It doesn't cover rate limits or what 'failed call' means at the HTTP level.

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 purpose, then the return contents, then the operational constraints (robots.txt, price). The long field enumeration is dense but each item is informative rather than padding; no sentence is redundant.

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 needn't explain return shapes, yet it still summarizes the payload and flags that issues arrive as plain sentences. Combined with the pricing and no-JS caveats, an agent has what it needs; only the when-not-to-use case is missing.

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% and the single url parameter is fully documented with an example, so the schema does the work. The description adds nothing about accepted URL forms (it doesn't confirm that bare domains are accepted, which the schema does) or normalization behavior.

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 states a specific resource and scope: 'SEO and sharing metadata of one web page, read from its HTML without JavaScript,' then enumerates the exact fields returned. An agent knows precisely what comes back. It stops short of 5 because it doesn't distinguish itself from plausible siblings like 'read', 'lang' or 'robots'.

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?

Usage is only implied: an agent can infer this is the tool for auditing a page's SEO/meta tags. There is no explicit 'use this when...' or 'use X instead for...' guidance, and no mention of when the tool would be a poor fit (e.g. JS-rendered content, which it explicitly cannot read).

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