AnimatedWebs

Get my AnimatedWebs account

get_account

Read-onlyIdempotent

Returns the signed-in account's AnimatedWebs plan and today's usage (Pro prompt access or Prompt Pack credits, UI generations and Design AI requests used against the daily limits), links, the Design workspace URL, and on request the account's items. Use it to check whether a Pro prompt, generate_component or refine_component call will succeed, or to pick up earlier work; use get_pricing for plan prices and save_item to change saved items. include_items adds items: saved (templates, components and backgrounds saved with save_item or hearted on animatedwebs.com), unlocked (Pro templates already opened, so fetching their prompt again is free) and generated (prompt, model and date of each AI generation; the HTML itself is not stored). includeDesignConnect adds ready-to-paste setup for the separate AnimatedWebs Design MCP server; it contains a personal bearer token, so never write it to shared files. Counts are per UTC day. Read-only. Example: {"include_items":true,"items":"saved","items_limit":10}.

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": "get_account"
  }
}

Input Schema

Name	Required	Description	Default
`items`	No	With include_items: which list to return. all (default), saved, unlocked or generated.	all
`items_limit`	No	With include_items: entries per list, 1 to 50 (default 20).
`include_items`	No	true adds items (saved, unlocked and generated lists, newest first). Default false.
`includeDesignConnect`	No	true adds design.connect (Claude Code command, Cursor and VS Code config with a personal bearer token) and design.note. Default false keeps the token out of the reply.

Output Schema

Name	Required	Description
`plan`	Yes	Plan id, e.g. free, starter, pro or lifetime
`tier`	Yes
`items`	No	Only with include_items
`links`	Yes
`design`	Yes
`prompts`	Yes	'unlimited (Pro)' or the credit counts
`designAi`	Yes
`uiGenerations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 8, 2026

changedInput schema / properties / includeDesignConnect / description

Previous value: -"true adds design.connect (commands and config with a personal bearer token) and design.note. Default false keeps the token out of the reply."New value: +"true adds design.connect (Claude Code command, Cursor and VS Code config with a personal bearer token) and design.note. Default false keeps the token out of the reply."

addedInput schema / properties / include_items

Added value: +{
+  "default": false,
+  "description": "true adds items (saved, unlocked and generated lists, newest first). Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / items

Added value: +{
+  "default": "all",
+  "description": "With include_items: which list to return. all (default), saved, unlocked or generated.",
+  "enum": [
+    "all",
+    "saved",
+    "unlocked",
+    "generated"
+  ],
+  "type": "string"
+}

addedInput schema / properties / items_limit

Added value: +{
+  "default": 20,
+  "description": "With include_items: entries per list, 1 to 50 (default 20).",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / items

Added value: +{
+  "additionalProperties": false,
+  "description": "Only with include_items",
+  "properties": {
+    "generated": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "createdAt": {
+            "type": "string"
+          },
+          "model": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "prompt": {
+            "description": "First 200 characters",
+            "type": "string"
+          },
+          "tool": {
+            "description": "ui (component generator) or design (Design AI)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "prompt",
+          "model",
+          "createdAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "saved": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "description": "Template slug, component id or background slug",
+            "type": "string"
+          },
+          "savedAt": {
+            "type": "string"
+          },
+          "title": {
+            "description": "null when the item left the catalog",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "enum": [
+              "template",
+              "component",
+              "background"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "type",
+          "id",
+          "title",
+          "url",
+          "savedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unlocked": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "unlockedAt": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "url",
+          "unlockedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedNov 2, 2026

addedInput schema / properties / includeDesignConnect

Added value: +{
+  "default": false,
+  "description": "true adds design.connect (commands and config with a personal bearer token) and design.note. Default false keeps the token out of the reply.",
+  "type": "boolean"
+}

addedOutput schema / properties / design

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "connect": {
+      "additionalProperties": false,
+      "description": "Only with includeDesignConnect",
+      "properties": {
+        "claudeCode": {
+          "description": "Shell command",
+          "type": "string"
+        },
+        "cursor": {
+          "additionalProperties": {},
+          "description": "mcp.json fragment",
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "vscode": {
+          "additionalProperties": {},
+          "description": "VS Code mcp.json fragment",
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "claudeCode",
+        "cursor",
+        "vscode"
+      ],
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "workspace": {
+      "description": "Design workspace URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "workspace"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "plan",
-  "tier",
-  "prompts",
-  "uiGenerations",
-  "designAi",
-  "links"
-]New value: +[
+  "plan",
+  "tier",
+  "prompts",
+  "uiGenerations",
+  "designAi",
+  "design",
+  "links"
+]

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantive behavior: counts are per UTC day, generated items retain prompt/model/date but not the HTML, unlocked templates make re-fetching a prompt free, and includeDesignConnect embeds a personal bearer token that must never be written to shared files. The only minor gap is that it doesn't describe reply ordering/structure beyond 'newest first', though an output schema exists.

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?

Content is front-loaded (what it returns, then when to use it, then parameter behavior) and every sentence supplies decision-relevant information. It is a dense single block, however, and the parameter discussion would scan faster as a short list.

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?

For a read-only account snapshot with an output schema already documenting return shape, this covers everything an agent needs: cost/limit meaning, UTC day boundary, optional item expansion, and the credential hazard. Nothing required 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 coverage is 100%, so the baseline is 3; the description earns above that by defining what each list actually contains (saved = templates/components/backgrounds, unlocked = Pro templates already opened, generated = prompt/model/date) and by explaining why includeDesignConnect is sensitive. It still relies on the schema for the items_limit bounds and default, so it isn't fully self-contained.

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?

The description opens with a concrete verb+resource pairing ('Returns the signed-in account's AnimatedWebs plan and today's usage') and enumerates the returned surface (plan, usage counters, links, Design workspace URL, optional items). It explicitly distinguishes itself from get_pricing and save_item by name, so an agent can route without opening the 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?

It gives an explicit when-to-use clause tied to concrete siblings ('check whether a Pro prompt, generate_component or refine_component call will succeed, or to pick up earlier work') and names alternatives with their conditions ('use get_pricing for plan prices and save_item to change saved items'). Both use and non-use paths are covered.

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.