Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)

Search UI animations and micro-interactions

search_motion

Read-only

Search the motion library: UI animations and micro-interactions (button presses, toggles, toasts, number tickers, check-offs, thinking states, hover effects, sounds) from open-source libraries and designers' recordings, each with an exact spec and most with vanilla code. Any word can match ("habit streak tick" finds check-offs); more matched words rank higher. Use it when an interactive element should feel finished, then get_motion for the spec and code. To audit a whole library: source= fields=brief lists every entry in one call, with counts by category and by the source's own sections, and which code each has (vanilla, react, install, npm). For a whole UI, suggest_polish maps its parts to entries and sounds.

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

Input Schema

Name	Required	Description	Default
`q`	No	Keywords, e.g. "copy button", "toast", "number ticker", "thinking shimmer".
`basis`	No	Where the numbers come from - code (exact, read from source), video (measured from a recording) or rebuild.
`limit`	No	Maximum results, 1 to 50 (100 with fields=brief, its default).
`fields`	No	brief gives one short row per entry (id, title, category, group, code), up to 100 per call.	full
`offset`	No	Results to skip; pass nextOffset from the previous page.
`source`	No	Comma-separated source ids, as listed by get_motion_guidelines.
`hasCode`	No	Only entries with working code (a vanilla rebuild or original source).
`trigger`	No	Comma-separated triggers (OR) - hover, press, click, focus, load, scroll, drag, state-change, loop, type.
`category`	No	Comma-separated categories (OR): button, toggle, input, list, card, navigation, overlay, toast, loader, text, number, chat-ai, cursor, scroll, transition, icon, feedback, media, sound, other.

Output Schema

Name	Required	Description	Default
`code`	No
`next`	No
`total`	No
`entries`	No
`message`	No
`partial`	No
`byCategory`	No
`nextOffset`	No
`bySourceGroup`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 31, 2026

addedInput schema / properties / fields

Added value: +{
+  "default": "full",
+  "description": "brief gives one short row per entry (id, title, category, group, code), up to 100 per call.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Maximum results, 1 to 50."New value: +"Maximum results, 1 to 50 (100 with fields=brief, its default)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Results to skip; pass nextOffset from the previous page.",
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / byCategory
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / bySourceGroup
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / code
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / nextOffset
```
Added value: +{
+  "type": "integer"
+}
```

Changed6 schema fields changedOct 30, 2026

addedInput schema / properties / limit / maximum
```
Added value: +50
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedInput schema / properties / source / description

Previous value: -"Comma-separated source ids, as listed by getMotionGuidelines."New value: +"Comma-separated source ids, as listed by get_motion_guidelines."

removedOutput schema / properties / entries / items

Removed value: -{
-  "properties": {
-    "basis": {
-      "enum": [
-        "code",
-        "video",
-        "rebuild"
-      ],
-      "type": "string"
-    },
-    "category": {
-      "type": "string"
-    },
-    "credit": {
-      "properties": {
-        "name": {
-          "type": "string"
-        },
-        "url": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "demoUrl": {
-      "description": "Live standalone demo.",
-      "nullable": true,
-      "type": "string"
-    },
-    "hasOriginalCode": {
-      "type": "boolean"
-    },
-    "hasVanillaCode": {
-      "type": "boolean"
-    },
-    "id": {
-      "type": "string"
-    },
-    "posterUrl": {
-      "type": "string"
-    },
-    "source": {
-      "properties": {
-        "id": {
-          "type": "string"
-        },
-        "license": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "summary": {
-      "type": "string"
-    },
-    "tags": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": {
-      "type": "string"
-    },
-    "triggers": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "url": {
-      "description": "The entry's page on Screenrove.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / partial / description

Removed value: -"True when no entry matched every word."

AddedOct 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld=false and non-destructive, so the safety bar is low; the description adds real behavioral detail beyond them — any-word matching and rank-by-number-of-matched-words, plus that results carry exact specs and mostly vanilla code. It stops short of describing result fields or when a query is too broad, which the output schema presumably covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Leads with the resource definition, then matching semantics, then the recommended follow-up call, then two scoped advanced uses — all in three sentences with no filler. The parenthetical lists are dense but each item adds discriminating vocabulary for retrieval.

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 9-parameter read-only search with full schema coverage, enums, and an output schema, the description supplies the remaining judgment calls: what the corpus contains, how matching ranks, and which sibling to call before and after. Nothing an agent needs to invoke 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 is 3, but the description earns more by explaining query semantics ("habit streak tick" finds check-offs; more matched words rank higher) that the schema does not, and by tying source to get_motion_guidelines and hasCode to "working code". Minor blemish: the description says 50 max (100 with fields=brief) while the schema allows maximum 100, a small limit inconsistency an agent must reconcile.

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 ("Search the motion library") and immediately enumerates the resource's contents (button presses, toggles, toasts, tickers, sounds), so an agent knows exactly what is and isn't indexed. It also names the boundaries against siblings — get_motion for spec/code and suggest_polish for whole-UI mapping — making it distinguishable 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?

Gives explicit triggers ("when an interactive element should feel finished"), an explicit two-step flow ("then get_motion for the spec and code"), and explicit alternative routes for adjacent tasks ("To audit a whole library: source=<id> fields=brief", "For a whole UI, suggest_polish"). Both the when and the when-not are covered.

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

All Screenrove: UI Design Reference & Screenshots (free Mobbin alternative) 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.

Resources

Need Help?