← URLMe.linkCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to URLMe.link
Snapshot Oct 9, 2026 · 18:03 UTC · version 1.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Connect URLMe and learn how to create branded short links and manage them from a chat or coding project.",
"included_files": [],
"name": "get-started",
"skill_md_contents": "---\nname: get-started\ndescription: Connect URLMe and learn how to create branded short links and manage them from a chat or coding project.\n---\n\nHelp the user connect their existing URLMe workspace through the plugin's OAuth flow. After the connection succeeds, call `get_profile` and `get_usage` to confirm the selected workspace and its current capacity.\n\nExplain that URLMe can create standard or branded short links on a connected custom domain, choose custom aliases, add private descriptions, schedule expiration, list recent links with redirect analytics, update private descriptions, pause or resume redirects, permanently expire links, identify the connected workspace, and report current plan usage and resource counts. Offer these starter examples:\n\n- “Shorten this URL and label it for my launch.”\n- “Create a branded link on my connected domain with the alias welcome.”\n- “Show my newest links, redirect counts, and recent activity.”\n- “Pause the campaign link.”\n- “How much of my plan have I used?”\n\nWhen the user asks to create a link, preserve the destination exactly and pass a description only when the user provided or requested one. Use the workspace's default URLMe domain unless the user names a connected custom domain. Never invent a short URL; return only the URL produced by `create_short_link`.\n\nThe URLMe product also provides searchable workspace history, DNS and HTTPS custom-domain setup, bulk creation, private tags and filtering, UTM parameters, destination changes, deletion, downloadable QR codes, CSV export, REST API automation with idempotent retries, per-integration API-key creation and revocation, and subscription management through its web console or REST API. These actions are not exposed by this MCP server. When the user requests one of them, explain the boundary and direct the user to the appropriate URLMe console or API workflow rather than claiming the action was completed.\n\nBefore calling `expire_link`, identify the exact link and ask for confirmation because expiration is permanent. Pause and resume links only when the target link is unambiguous. Do not request, display, or store URLMe API keys in chat; OAuth supplies the connection.\n"
}SHA-256 of public snapshot: bfc546fe711e9a36c36a26c31d84f826b46a4b05b5b1b9e6b0e3e510caad2135