Screenrove

Get a product's design guide

get_design

Read-only

Get the measured design guide for a product: observed font families, color palette, type scale, layout patterns, spacing values, and component observations. Marketing site and product UI are measured separately.

Use this when you want to match a competitor's design system, understand their visual language, or borrow their typography and color choices for your own project.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the guide is 'measured/observed' and that marketing and product surfaces are measured separately, which is useful context, but return format and granularity are left to the output schema.

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?

Three tight sentences, front-loaded with the concrete deliverable before the usage guidance. The 'measured separately' clause slightly overlaps the already-documented context enum, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not document return values, and it still previews the field categories helpfully. Inputs are fully covered by the schema; only a pointer to related tools (e.g., get_product, list_products) 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% and both parameters are documented, so the baseline is 3. The description slightly exceeds it by explaining that marketing site and product UI are distinct measured datasets, reinforcing why the 'context' enum exists and what happens when it is omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the measured design guide for a product') and enumerates the concrete contents (font families, palette, type scale, spacing, components), which lets an agent distinguish it from get_product or get_screen. It stops short of explicitly naming the sibling it is not.

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?

The second sentence gives clear triggering contexts: matching a competitor's design system, understanding visual language, borrowing typography/colors. No exclusions or named alternatives are given, so it falls just short of the top band.

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

All Screenrove tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?