Web Page Title Grounding Data

Overview

Send a web address to parse the live document over HTTP. The endpoint inspects the markup and extracts the text content inside the title tag. On paid tiers, the response also includes a list of all H1 headings located within the page body.

Live Test Web Page Title Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as WebPageTitleGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "WebPageTitleGroundingData",
  "arguments": {
    "url": "https://en.wikipedia.org/wiki/HTML_element"
  }
}

You do not name the tool yourself; the model picks it. Asking about https://en.wikipedia.org/wiki/HTML_element in the terms this source covers is enough for it to reach for WebPageTitleGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10

{
  "status": "ok",
  "error": null,
  "data": {
    "title": "HTML element - Wikipedia",
    "h1": [
      "HTML element"
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at title: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Bookmark Link Cards

Social bookmarking platforms generate readable cards by pulling page titles whenever members save external web links.

SEO Metadata Auditing

Audit web pages across a client domain to verify that HTML title tags exist and match target requirements.

Reading List Management

When readers submit articles to an aggregator, the system attaches live page titles to label each entry automatically.

Chat Message Previews

Messaging services parse shared URLs on post to show clear discussion context before members click outbound links.

Other ways to use Web Page Title Grounding Data

Set up Web Page Title Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Domain Data: