Skip to main content
Glama
Sign In
awwwards-mcp

awwwards-mcp

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_hover_census

Read-only

Count and inspect :hover CSS rules on any live page, sampling interactive elements to report which properties change on hover with transition duration and easing.

Instructions

:hover interaction census of a live page: counts hover rules, samples up to 20 interactive elements, and reports which CSS properties change on hover with transition duration and easing. Use it to reproduce micro-interactions and verify interaction-state coverage. On mobile the hover loop is skipped and a note is returned. compact=true returns a token-diet summary. Runs on any URL — does not fetch awwwards.com.

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_hover_census"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute page URL to census
compactNotoken-diet summary: sample style bodies become a selector list + count
viewportNodesktop = 1440x900 (default); mobile = 390x844 iPhone-class with deviceScaleFactor 3, isMobile + hasTouchdesktop
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.15.1
    • addedInput schema / properties / waitStrategy / description
      Added value: +"'load' plus a settle works on heavy sites; 'networkidle' (default) waits for total quiet"
  2. 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"
  3. Changed1 schema field changedv1.13.0
    • removedInput schema / additionalProperties
      Removed value: -false
  4. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "token-diet summary: sample style bodies become a selector list + count",
+  "type": "boolean"
+}
  5. Addedv1.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive; the description adds genuinely new behavior: the hover loop is skipped on mobile with a note returned, and compact=true changes the output shape to a token-diet summary. It does not explain why idempotentHint is false (live page, results vary per capture), which would have completed the picture.

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 operation and outputs, and every clause except one carries information. The trailing 'does not fetch awwwards.com' is an oddly specific non-capability that reads as noise without a named sibling to contrast against.

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?

With no output schema, the description still conveys what the agent gets back (counts, sampled elements, changed properties with timing), how the return changes under compact and mobile, and that it works on arbitrary URLs. Nothing essential for a correct invocation is missing.

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 description coverage is 100%, so all five parameters are already documented, and the description only echoes compact's token-diet behavior while tying viewport to the mobile skip. reducedMotion and waitStrategy get no added meaning in the description, so baseline 3 applies.

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 (':hover interaction census of a live page') and enumerates the concrete outputs: hover rule counts, up to 20 sampled interactive elements, changed CSS properties with transition duration and easing. This is clearly distinguishable from sibling motion/scroll tools such as analyze_scroll_map or record_site_motion.

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?

'Use it to reproduce micro-interactions and verify interaction-state coverage' gives a clear use context, and the mobile caveat tells the agent when the tool's output will be degraded. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is strong but not routing-complete.

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