FreeTier Agent API

page-meta

page_meta

Read-only

3 free MCP calls per day (all tools together), then $0.0025 USDC via x402 or card credits (paid in-band: params._meta["x402/payment"]). Fetch a public web page (robots.txt respected) and return title, meta description, canonical, Open Graph/Twitter tags, language, headings, link counts, HTTP status. When to use: Use page-meta for title, description, Open Graph and headings only; for full content use page-rag.

Input Schema

Name	Required	Description	Default
`url`	Yes	absolute http(s) URL

Output Schema

Name	Required	Description	Default
`h1`	No
`h2`	No
`og`	No
`url`	No
`lang`	No
`links`	No
`title`	No
`status`	No
`sources`	No
`twitter`	No
`canonical`	No
`final_url`	No
`description`	No
`content_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / description

Previous value: -"Inferred from a real response captured on 2026-10-24; extra fields may appear, null-valued fields are untyped."New value: +"Inferred from a real response captured on 2026-10-26; extra fields may appear, null-valued fields are untyped."

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Inferred from a real response captured on 2026-10-24; extra fields may appear, null-valued fields are untyped.",
+  "properties": {
+    "canonical": {},
+    "content_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {},
+    "final_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "h1": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "h2": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "lang": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "properties": {
+        "external": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "internal": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "og": {
+      "properties": {},
+      "type": "object"
+    },
+    "sources": {
+      "items": {
+        "properties": {
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "twitter": {
+      "properties": {},
+      "type": "object"
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds crucial operational context that annotations and schema lack, specifically the rate limit and cost structure ($0.0025 USDC and 3 free calls per day). It also mentions it respects robots.txt.

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?

The description is efficiently structured into two distinct parts: function/cost and usage guidelines. While it uses two sentences, the information density is extremely high and achieves its goals without unnecessary fluff.

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

Completeness5/5

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

The description is complete enough for an agent to decide if this tool meets the user's needs. Given the clarity on what it fetches (metadata) and its limitations (not full content), the agent has all necessary contextual information to select it correctly.

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?

Since the input schema provides 100% coverage for the single 'url' parameter, the description offers minimal semantic value beyond the schema itself. It does not provide specialized context for the URL parameter.

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 defines the tool's function by stating it fetches a public web page and returns a specific set of meta-data (title, canonical, Open Graph tags, etc.). It successfully differentiates itself from the sibling tool page-rag by specifying it returns only metadata.

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

Usage Guidelines5/5

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

It provides a highly actionable usage guideline by contrasting its purpose with that of page-rag. The agent is explicitly instructed to use page-meta for metadata and page-rag for full content.

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

All FreeTier Agent API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?