Sitemap Generator SkillSitemap Generator Skill

OnlineCredit Usage:1 per callTool:SitemapGeneratorSkill

The tool

The API accepts URLs as strings or objects with custom priority, change frequency, and last modified dates, with support for base URL prefixing.

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

Tool call
{
  "name": "SitemapGeneratorSkill",
  "arguments": {
    "urls": "[\"/about\", \"/contact\", {\"url\": \"/blog\", \"priority\": 0.8}]"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about ["/about", "/contact", {"url": "/blog", "priority": 0.8}] in the terms this source covers is enough for it to reach for SitemapGeneratorSkill on its own.

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.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, 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.

ArgumentTypeExampleDescription
urlsRequiredarray["/about", "/contact", {"url": "/blog", "priority": 0.8}]Array of URLs (strings or objects with url, priority, changeFreq, lastMod)
baseUrlstringhttps://example.comBase URL to prepend to relative paths
changeFreqstringweeklyDefault change frequency One of: always, hourly, daily, weekly, monthly, yearly, never.
prioritynumber0.5Default priority
includeLastModbooleantrueInclude lastmod dates in sitemap

What the model gets back

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

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "sitemap": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://example.com/</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/about</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/contact</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.5</priority>\n  </url>\n  <url>\n    <loc>https://example.com/blog</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>daily</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url>\n    <loc>https://example.com/products</loc>\n    <lastmod>2025-12-16</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.9</priority>\n  </url>\n</urlset>",
    "urlCount": 5,
    "sizeBytes": 892,
    "sizeKb": 0.87,
    "format": "XML",
    "protocol": "sitemaps.org/0.9",
    "settings": {
      "defaultChangeFreq": "weekly",
      "defaultPriority": 0.5,
      "includeLastMod": true,
      "baseUrl": "https://example.com"
    }
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
sitemapstring<?xml version="1.0" encoding="UTF-8"?> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"> <url> <loc>https://example.com/</loc> <lastmod>2025-12-16</lastmod> <changefreq>weekly</changefreq> <priority>0.5</priority> </url> <url> <loc>https://example.com/about</loc> <lastmod>2025-12-16</lastmod> <changefreq>weekly</changefreq> <priority>0.5</priority> </url> <url> <loc>https://example.com/contact</loc> <lastmod>2025-12-16</lastmod> <changefreq>weekly</changefreq> <priority>0.5</priority> </url> <url> <loc>https://example.com/blog</loc> <lastmod>2025-12-16</lastmod> <changefreq>daily</changefreq> <priority>0.8</priority> </url> <url> <loc>https://example.com/products</loc> <lastmod>2025-12-16</lastmod> <changefreq>weekly</changefreq> <priority>0.9</priority> </url> </urlset>Generated XML sitemap content following sitemaps.org protocol
urlCountnumber5Total number of URLs included in the generated sitemap
sizeBytesPremiumnumber892Total size of generated sitemap in bytes
sizeKbPremiumnumber0.87Total size of generated sitemap in kilobytes
formatstringXMLOutput format type of generated sitemap content
protocolstringsitemaps.org/0.9Sitemap protocol version used for XML generation
settingsobject{…}
settings.defaultChangeFreqstringweeklyDefault change frequency setting applied to all URLs
settings.defaultPrioritynumber0.5Default priority value assigned to all URLs
settings.includeLastModbooleantrueFlag indicating if last modified dates are included
settings.baseUrlstringhttps://example.comBase URL used to create absolute paths for relative URLs

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Sitemap Generator Skill

Set up Sitemap Generator 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.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →

Frequently asked questions

Do I have to tell the agent to use SitemapGeneratorSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?