Skip to main content
Glama
Sign In

AnimatedWebs

by com.animatedwebs
OverviewDiscussionsAdmin

Get an AnimatedWebs cinematic background

get_background
Read-onlyIdempotent

Returns one AnimatedWebs cinematic video background by slug: on Pro and Lifetime the clean watermark-free MP4 URL plus an HTML snippet for a muted, looping, autoplaying hero video; on other plans the watermarked preview URL, clean: null and the plan required (not an error). Use it after search_catalog (kind backgrounds); use get_template for full website templates. A clean file counts toward the fair-use cap shared with get_component source (40 per 10 minutes, 150 a day, 500 a week; never blocks one already opened today). Read-only. Unknown slugs return an error. Example: {"slug":"aurora-loop"}.

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>"
    },
    "name": "get_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBackground slug exactly as returned by search_catalog (kind backgrounds), e.g. 'aurora-loop'.

Output Schema

NameRequiredDescriptionDefault
urlNoClean MP4 URL (Pro only)
planNo
slugYes
cleanNoAlways null for non-Pro
licenseNo
previewNoWatermarked preview (non-Pro only)
pricingNo
snippetNoHTML video element (Pro only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Background slug exactly as returned by search (kind backgrounds)."New value: +"Background slug exactly as returned by search_catalog (kind backgrounds), e.g. 'aurora-loop'."
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Background slug exactly as returned by search_backgrounds."New value: +"Background slug exactly as returned by search (kind backgrounds)."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses plan-dependent return shapes (clean MP4 plus HTML snippet vs watermarked preview with clean: null and plan required, explicitly not an error), and that unknown slugs error out. It also documents the fair-use cap (40/10min, 150/day, 500/week) and that an already-opened item is never blocked, which the annotations cannot convey.

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 the return contract and plan gating, then the routing guidance, then the limits. Dense but nearly every clause carries information; the parenthetical quota figures make one sentence heavy, though they earn their place.

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?

Complete for a one-parameter read tool: plan gating, error behavior, quota interaction with get_component source, and the autoplay/loop/muted snippet context are all covered. An output schema exists, so the extra return detail is bonus rather than a gap-filler.

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

Parameters3/5

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

Schema coverage is 100% and the single slug parameter already documents provenance from search_catalog with an example. The description repeats the example and adds the unknown-slug error behavior, but contributes no new syntax or format meaning beyond the schema. Baseline 3 is appropriate.

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 ("Returns one AnimatedWebs cinematic video background by slug") and immediately distinguishes itself from get_template ("use get_template for full website templates"). An agent can identify the tool 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?

Explicitly sequences the call ("Use it after search_catalog (kind backgrounds)") and names the alternative for a different need (get_template). It also states the when-not condition implicitly by describing plan-gated behavior, so nothing about tool selection is left to inference.

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

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