AnimatedWebs

Save an AnimatedWebs item

save_item

Idempotent

Saves, unsaves or lists the signed-in account's favorite AnimatedWebs templates, UI components and cinematic backgrounds. Use it when the user wants to keep an item for later or see what they kept; use get_account with include_items for the full picture (saved plus unlocked and generated items). action save adds the item (saving twice is a no-op), unsave removes only the bookmark (removing an unsaved item is a no-op, and it can be saved again), list returns saved items newest first, optionally only one type. Saved templates are the same list as the Save heart on animatedwebs.com and the dashboard. The id must exist in the catalog. Examples: {"action":"save","type":"template","id":"aurora-site"}, {"action":"list","type":"component"}.

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": {
      "action": "<action>"
    },
    "name": "save_item"
  }
}

Input Schema

Name	Required	Description
`id`	No	Required for save and unsave: template slug, component id or background slug exactly as returned by search_catalog, e.g. 'aurora-site'.
`type`	No	template (default for save and unsave), component or background. For list, filters to one type; omit to list all.
`limit`	No	For list: how many items, 1 to 50 (default 20).
`action`	Yes	save: add a favorite. unsave: remove it. list: show saved items.

Output Schema

Name	Required	Description
`item`	No	For save and unsave
`items`	No	For list, newest first
`saved`	No	For save and unsave: whether the item is saved after the call
`action`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, but the description adds substantive behavior beyond them: saving twice is a no-op, unsave removes only the bookmark and the item can be saved again, unsaving an unsaved item is a no-op, list returns newest first, and the id must exist in the catalog. It also anchors the semantics to the visible Save heart on animatedwebs.com and the dashboard, which is real context an agent cannot get from annotations.

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?

Front-loaded with purpose, then the alternative, then per-action semantics, then examples — a logical order with no filler sentences. It is somewhat dense and the trailing examples partially restate earlier rules, which keeps it just short of a 5.

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

Completeness5/5

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

An output schema exists, so return values need not be explained; the description instead covers the edge cases that matter for a three-action bookmark tool (no-op re-saves, re-savable after unsave, catalog existence requirement, list ordering and type filter). Nothing needed to call it correctly is missing.

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 description coverage is 100%, so the baseline would be 3. The description goes beyond it by stating the id must exist in the catalog and by giving concrete call examples for each action shape, though it repeats the type default that the schema already documents.

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?

Opens with a specific verb set (saves, unsaves, lists) and a precise resource scope (the signed-in account's favorite templates, UI components and backgrounds). It also distinguishes itself from the sibling get_account by noting that get_account with include_items gives the full picture, so an agent can separate the two 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 Guidelines5/5

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

Explicitly states the user intent that selects this tool ('keep an item for later or see what they kept') and names the alternative (get_account with include_items) plus the condition that favors it. Per-action guidance for save, unsave and list is spelled out rather than implied.

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

All AnimatedWebs 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.