ATTIM

Set links

set_links

DestructiveIdempotent

Replace every link on a profile or link page. Pass ids from list_links to keep click history; links you omit are deleted. Order is the order within each section; at most 2 pinned, 50 in all. Links with the same group show together under its name; null removes the group. trackingEnabled:false links are not counted and keep their place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "links": "<links>"
    },
    "name": "set_links"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`links`	Yes
`expectedVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / links / items / additionalProperties
```
Removed value: -false
```
- changedInput schema / properties / links / items / properties / id / description
```
Previous value: -"Existing link id from list_links; keeps click history."New value: +"Existing link id; keeps its click history."
```
- removedInput schema / properties / links / items / properties / id / maxLength
```
Removed value: -64
```
- removedInput schema / properties / links / items / properties / id / minLength
```
Removed value: -1
```
- removedInput schema / properties / links / items / properties / label / minLength
```
Removed value: -1
```
- removedInput schema / properties / links / items / properties / url / maxLength
```
Removed value: -2048
```
- removedInput schema / properties / links / items / properties / url / minLength
```
Removed value: -1
```
- removedInput schema / properties / slug / minLength
```
Removed value: -1
```
First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true) by spelling out exactly what gets destroyed (omitted links, including click history unless ids are passed) and the hard limits: at most 2 pinned and 50 total. It also explains ordering, group coalescing, null-removes-group, and the trackingEnabled=false exception to counting and placement.

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

Conciseness5/5

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

The destructive replace semantics are front-loaded in the first sentence, then each following clause adds a non-obvious rule with no filler. Dense but every sentence earns its place.

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

Completeness4/5

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

For a destructive whole-collection replace with no output schema and no annotation-documented concurrency behavior, the description covers the critical risks well. The notable gap is expectedVersion: an agent has no idea it must supply a version to avoid clobbering concurrent edits.

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?

With 0% schema description coverage the description must carry the load, and it explains id (keeps click history), section ordering, group behavior including null, and trackingEnabled. It leaves expectedVersion completely unexplained for an optimistic-concurrency field, and never mentions disabled, so the coverage is strong but not complete.

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?

States a specific verb and resource: 'Replace every link on a profile or link page.' The replace semantics (not append/patch) are explicit and distinguish it from list_links and the other site/profile siblings.

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?

Gives concrete usage direction: 'Pass ids from list_links to keep click history; links you omit are deleted', which routes the agent to list_links first and warns of the replace consequence. It stops short of an explicit when-not-to-use statement or naming an alternative mutation tool.

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

All ATTIM tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?