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 URL Title Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as URLTitleSkill. 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": "URLTitleSkill",
"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 skill covers is enough for it to reach for URLTitleSkill on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every skill 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": {
"vervekit": {
"url": "https://api.vervekit.com/v1/mcp"
}
}
}https://api.vervekit.com/v1/mcpPer-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.
| Argument | Type | Description |
|---|---|---|
urlRequired | string | The URL of the web page to get the title of url |
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.
{
"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.
| Field | Type | Example | Description |
|---|---|---|---|
title | string | HTML element - Wikipedia | The HTML title tag content of the web page |
h1Premium | array | ["HTML element"] | Array of all H1 heading elements found on the page |
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.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This skill is not part of VerveKit. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
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 URL Title Skill
Set up URL Title Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.
Related
More in Domain Data: