Skip to main content
Glama
Sign In
awwwards-mcp

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_scroll_map

Read-only

Audit a live page's per-element scroll animations: what animates, CSS properties, timing, triggers, and scrub curves. Rerun with reduced motion to check degradation.

Instructions

Per-element motion census of a live page: what animates, its CSS properties, duration, delay, easing, and what triggered it (GSAP ScrollTrigger, native CSS scroll()/view() timelines, data attributes, SMIL/SVG). Includes svgStrokes list for stroke draw-in effects. Runs on any URL you give it (builds, references) — does not fetch awwwards.com. Run twice (with reducedMotion) to audit prefers-reduced-motion degradation. Optional scrubProbe drives the page and returns real progress curves per scrubbed trigger. compact=true returns a token-diet summary. Every payload also carries a choreography block: stagger hints (hint selector/value/source, groups) distilled from GSAP tween vars and stepped delays across sibling animations.

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": {
      "url": "<url>"
    },
    "name": "analyze_scroll_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute page URL to census
compactNotoken-diet summary: keyframes/props/durations and scrubCurves replaced by counts; all numerics and triggers stay. It cannot feed build_gsap_stub/build_motion_manifest (anims[] is omitted) — use compact=false for that handoff
viewportNodesktop = 1440x900 (default); mobile = 390x844 iPhone-class with deviceScaleFactor 3, isMobile + hasTouchdesktop
scrubProbeNodrive the page through up to 8 scroll steps and sample each scrubbed trigger's progress curve (adds seconds)
waitStrategyNo'load' plus a settle works on heavy sites; 'networkidle' (default) waits for total quiet
reducedMotionNoEmulate prefers-reduced-motion: reduce for this capture

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • changedInput schema / properties / compact / description
      Previous value: -"token-diet summary: keyframes/props/durations and scrubCurves replaced by counts; all numerics and triggers stay"New value: +"token-diet summary: keyframes/props/durations and scrubCurves replaced by counts; all numerics and triggers stay. It cannot feed build_gsap_stub/build_motion_manifest (anims[] is omitted) — use compact=false for that handoff"
  2. Changed1 schema field changedv1.15.1
    • addedInput schema / properties / waitStrategy / description
      Added value: +"'load' plus a settle works on heavy sites; 'networkidle' (default) waits for total quiet"
  3. Changed1 schema field changedv1.14.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv1.13.0
    • removedInput schema / additionalProperties
      Removed value: -false
  5. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "token-diet summary: keyframes/props/durations and scrubCurves replaced by counts; all numerics and triggers stay",
+  "type": "boolean"
+}
  6. Changed1 schema field changedv1.11.0
    • addedInput schema / properties / scrubProbe
      Added value: +{
+  "description": "drive the page through up to 8 scroll steps and sample each scrubbed trigger's progress curve (adds seconds)",
+  "type": "boolean"
+}
  7. Addedv1.9.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, non-destructive, openWorld), and the description adds genuinely new behavioral facts: it drives/navigates the page, scrubProbe has a measurable time cost ('adds seconds') and an 8-step cap, compact changes the payload shape and breaks the build_gsap_stub/build_motion_manifest handoff, and every payload carries a choreography block. That is real context an agent could not infer from the 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 the core purpose, then scoped facts in roughly descending importance; no filler sentences. The single dense finish covering the choreography block and its hint selector/value/source sub-fields is information-heavy but slightly hard to parse in one pass.

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?

There is no output schema, yet the description still explains the return shape (per-element animation records, svgStrokes, choreography stagger hints, compact counts). Combined with the time-cost warning for scrubProbe, an agent has what it needs to call this correctly and interpret the result.

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 3 is the floor the schema alone already earns. The description adds workflow-level meaning on top – reducedMotion is framed as a second-pass audit, scrubProbe as 'real progress curves per scrubbed trigger,' compact as a lossy summary – rather than merely restating enum values.

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+resource: a 'per-element motion census of a live page,' then enumerates exactly what is measured (CSS properties, duration, delay, easing, trigger source). This is readily distinguishable from siblings like analyze_hover_census, get_motion_dna, or record_site_motion 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?

Gives concrete operating guidance: works on any URL you supply, does not fetch awwwards.com, run twice with reducedMotion to audit degradation, scrubProbe adds seconds, compact=true for token-diet. It does not explicitly name the sibling alternatives for motion data (e.g. record_site_motion, get_motion_dna), so routing is strong but not fully resolved by the description itself.

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

Deploy Server

Other Tools