Screenrove

Search screens

search_screens

Read-only

Search the UI reference catalog by keyword across titles, notes, page sections, and observed actions. Filter by product or kind (flow/marketing/product).

Use this to find design pattern examples like "pricing page", "empty state", "date picker", "onboarding step", "checkout form", "dashboard", "sign-up", "settings", etc. Returns the best matches with screen IDs you can pass to getScreen or getScreenImage.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Keywords to match, e.g. "pricing page", "empty state", "onboarding". Omit to list everything that matches the filters.
`kind`	No	Only return this kind of screen.
`limit`	No	Maximum results, 1 to 50.
`product`	No	Only return screens from this product id, e.g. linear, stripe, airbnb.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	No
`screens`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / product / description

Previous value: -"Only return screens from this product id, e.g. linear."New value: +"Only return screens from this product id, e.g. linear, stripe, airbnb."

changedInput schema / properties / q / description

Previous value: -"Keywords to match. Omit to list everything that matches the filters."New value: +"Keywords to match, e.g. \"pricing page\", \"empty state\", \"onboarding\". Omit to list everything that matches the filters."

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "screens": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "imageUrl": {
+            "type": "string"
+          },
+          "kind": {
+            "description": "flow is an onboarding step, marketing a public web page, product an in-app screen.",
+            "enum": [
+              "flow",
+              "marketing",
+              "product"
+            ],
+            "type": "string"
+          },
+          "notes": {
+            "type": "string"
+          },
+          "previewUrl": {
+            "description": "Screen-sized preview (the top of long pages). Present on pick options.",
+            "type": "string"
+          },
+          "product": {
+            "type": "string"
+          },
+          "productName": {
+            "description": "Present on pick options.",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly and non-destructive, so safety is covered. The description adds real behavioral context beyond that: the fields matched, the kind/product filter dimension, and the fact that results carry screen IDs consumable by getScreen/getScreenImage.

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: the primary purpose and filter capability come first, followed by example queries and the return-value hook. Slightly redundant in that example queries appear in both the tool description and the q parameter, but there is no wasted framing.

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 an output schema present, the description need not explain return values, and it still describes the crucial ID handoff. Combined with full schema coverage and read-only annotations, an agent has everything needed to invoke this correctly.

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 every parameter is already documented in the schema. The description restates the product/kind filters and query examples but adds no format, syntax, or edge-case detail beyond what the schema provides, 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 ('Search the UI reference catalog by keyword') and names the exact fields searched (titles, notes, page sections, observed actions). It also points to the follow-up tools getScreen and getScreenImage, making it distinguishable from read-oriented siblings like get_screen.

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?

Explicitly frames the use case with concrete queries ('pricing page', 'empty state', 'date picker'), which tells the agent when to reach for this tool. It stops short of stating when NOT to use it or how it differs from sibling search/list tools such as list_flows or pick_reference.

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?