Kempt Horizon Data Toolkit

Web page metadata

page_metadata

Read-only

Get title, description, canonical URL, Open Graph/Twitter tags, JSON-LD, favicon and feeds for a URL or HTML.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "page_metadata"
  }
}

Input Schema

Name	Required	Description
`url`	No	Public http(s) URL to fetch (robots.txt is honored). Optional if html is given; then used as base URL.
`html`	No	Raw HTML to process instead of fetching (max 3 MB).
`include`	No	Comma list or array of parts to return: metadata, markdown, text, links, images, headings. Default: metadata
`maxChars`	No	Cap on markdown/text length (1,000-500,000).
`mainContentOnly`	No	Strip nav, header, footer, sidebars, cookie banners and ads; keep the main article.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety and network-exposure profile is already covered. The description adds value by enumerating the payload an agent can expect (a substitute for the missing output schema), but says nothing about fetch failures, robots-blocked responses, rate limits, or what happens when both url and html are omitted.

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?

A single front-loaded sentence listing the concrete outputs, with no hedging or filler. Every clause names a deliverable an agent can use to decide relevance.

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?

With no output schema, the enumeration of return fields is genuinely useful, but it is incomplete: the `include` parameter unlocks markdown/text/links/images/headings extraction and `mainContentOnly`/`maxChars` alter the output substantially, none of which the description hints at. An agent reading only the description would underestimate what the tool does and miss its overlap with page_to_markdown.

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 the schema already documents url/html, include, maxChars and mainContentOnly in detail. The description only echoes the 'URL or HTML' input duality and adds nothing about `include` modes, size caps, or main-content stripping. Baseline 3 applies when the schema does the heavy lifting.

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 ('Get') and resource (page metadata) and enumerates the returned fields: title, description, canonical URL, OG/Twitter tags, JSON-LD, favicon, feeds. It does not differentiate itself from the close siblings page_extract and page_to_markdown, which matters because the schema's `include` parameter can also return markdown, text, links, images and headings – a capability the description never mentions.

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?

There is no when-to-use guidance and no alternative named, despite two sibling tools (page_extract, page_to_markdown) that overlap on the markdown/text/links extraction modes. The only contextual hint is 'for a URL or HTML', which is restated from the schema rather than being routing guidance.

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

All Kempt Horizon Data Toolkit 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?