Overview
URL Encoder/Decoder works by converting special characters and spaces into percent-encoded format (%XX) for safe URL transmission or decoding percent-encoded strings back to original text. Essential for query parameters and URL construction.
Live Test URL Encode/Decode Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as URLEncodeDecodeSkill. 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": "URLEncodeDecodeSkill",
"arguments": {
"text": "Hello World!"
}
}You do not name the tool yourself; the model picks it. Asking about Hello World! in the terms this skill covers is enough for it to reach for URLEncodeDecodeSkill 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 |
|---|---|---|
textRequired | string | The text to encode |
actionOptional | string | The action to performencodedecodedefault encode |
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": {
"action": "encode",
"original": "Hello World & Goodbye",
"encoded": "Hello%20World%20%26%20Goodbye",
"length": 29
}
}
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 |
|---|---|---|---|
action | string | encode | The encoding or decoding action that was performed |
original | string | Hello World & Goodbye | The original text input before encoding or decoding |
encoded | string | Hello%20World%20%26%20Goodbye | The resulting encoded or decoded text output |
lengthPremium | number | 29 | The total character length of the encoded or decoded output |
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 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- API Requests
- Encode query parameters and URL components before making API requests to ensure proper formatting
- Link Generation
- Generate properly encoded URLs for links, redirects, and sharing with special characters or spaces
- Form Handling
- Encode form data for URL submission or decode URL-encoded form data received from submissions
- Search Queries
- Encode search terms and filters for URL-based search functionality and bookmarkable search results
Other ways to use URL Encode/Decode Skill
Set up URL Encode/Decode 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 Data Conversion: