Snip

Create or change a collection

save_collection

Creates a collection of the user's Snip.link links, or changes one (pass collection, its id from list_collections): its name, the line under it, its links in order, and whether it has a public page at snip.link/c/ that shows one button per live link, link-in-bio style. links replaces the collection's links in that order; leave it out to keep them. Free on every plan; the links themselves never change. Needs the user signed in to Snip.link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_collection"
  }
}

Input Schema

Name	Required	Description
`name`	No	The collection's name, shown on its page.
`slug`	No	The page's address after /c/: lowercase letters, digits and dashes. Left out, one is made from the name.
`links`	No	The links in order, each by short URL, ending or id (see list_links). Replaces the collection's links.
`public`	No	true switches the public page on, false off. Off by default.
`collection`	No	The id of the collection to change. Leave it out to create one.
`description`	No	One line under the name on the page. null removes it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- changedInput schema / properties / links / items / maxLength
```
Previous value: -300New value: +2048
```
AddedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses the one behavior an agent could get wrong: `links` replaces the stored order wholesale, while omitting it keeps the existing links — and it reassures that the underlying links themselves are never modified, which is consistent with destructiveHint=false. It adds auth requirements, plan/pricing cost, and what the public page actually renders (one button per live link, link-in-bio style).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The create-or-change intent is front-loaded in the first clause, and the trailing sentences each carry a distinct fact (replacement semantics, cost, auth). The opening sentence is long and parenthetical, packing fields and page behavior together, which costs some scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations plus a fully documented schema cover safety and parameter meaning, and the description covers auth, cost and update-vs-create behavior. However, with no output schema, a create tool should say what it returns (the new collection, its id, or its public URL) — that gap leaves the agent unable to chain calls after creation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it frames `slug` as the address of the public page at snip.link/c/<address>, ties `public` to that page, and restates the replace-vs-keep semantics of `links`. It adds context the schema alone doesn't convey about how slug, public and the page relate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Creates a collection of the user's Snip.link links, or changes one" gives a specific verb plus resource and covers both create and update modes in one clause. It also names the sibling (list_collections) that supplies the id, so an agent can tell this apart from list_collections or save_page without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the routing rule explicitly: pass `collection` (with its id from list_collections) to change one, leave it out to create. It also gives prerequisites ("Needs the user signed in") and cost ("Free on every plan"). It does not name a when-not-to-use case or a sibling to prefer for other collection operations, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Snip tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?