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

Get a product's design guide

get_design

Read-only

Get a product's measured design guide: fonts, colour palette, type scale, layout and component observations, measured separately for its marketing site and product UI. Use it for "make it look like " or "trustworthy like ": take the tokens from here and the structure from its screens (search_screens with product, then get_screen_image). fonts gives each context's families by role (display, body, mono) with licence, a CSS fallback stack and the closest free alternative plus its ; use the free one unless the user has the licensed font.

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": {
      "productId": "<productId>"
    },
    "name": "get_design"
  }
}

Input Schema

Name	Required	Description	Default
`context`	No	Which surface to return. Omit for both.
`productId`	Yes	Product id from list_products, e.g. linear, stripe or airbnb.

Output Schema

Name	Required	Description	Default
`font`	No
`fonts`	No
`product`	No
`summary`	No
`contexts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026
- addedOutput schema / properties / fonts
```
Added value: +{
+  "type": "object"
+}
```

Changed2 schema fields changedOct 30, 2026

changedInput schema / properties / productId / description

Previous value: -"Product id from listProducts, e.g. linear, stripe or airbnb."New value: +"Product id from list_products, e.g. linear, stripe or airbnb."

removedOutput schema / properties / contexts / additionalProperties

Removed value: -{
-  "properties": {
-    "components": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "layout": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "palette": {
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "theme": {
-      "type": "string"
-    },
-    "type": {
-      "items": {
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contexts": {
+      "additionalProperties": {
+        "properties": {
+          "components": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "layout": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "palette": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "theme": {
+            "type": "string"
+          },
+          "type": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "font": {
+      "type": "string"
+    },
+    "product": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 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/non-destructive, so the description is free to spend its words on domain behavior: measurement is split per surface, and fonts come with role, licence, fallback stack and a free alternative plus its link, with a decision rule ('use the free one unless the user has the licensed font'). That is real operational guidance beyond the structured fields; a minor gap is that it doesn't say how the guide is scoped when 'product' has no marketing site.

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?

Purpose is front-loaded in the first clause, intent examples and sibling routing follow, and the font detail lands last. Only the final sentence is overloaded, stacking licence, fallback stack, free alternative and its <link> into one long clause.

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?

Both parameters are documented in-schema, an output schema covers the return shape, and the description supplies the one thing the schema can't: how to use this result together with the screen-search siblings. Nothing an agent needs 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 a point by explaining that the two surfaces are measured separately, which gives the `context` enum (marketing/product) practical meaning rather than leaving it as a bare switch.

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 ('measured design guide') and enumerates exactly what it returns: fonts, colour palette, type scale, layout and component observations, split by marketing vs product surface. It also implicitly separates itself from the screenshot siblings by defining this as the tokens source versus screens as the structure source.

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 concrete triggering intents ('make it look like <product>', 'trustworthy like <product>') and routes the complementary task explicitly: take tokens here, structure from search_screens then get_screen_image. The alternates are named, not implied.

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?