Screenrove

Get one product

get_product

Read-only

Get a product's full collection: coverage notes, design summary, and every captured screen grouped into onboarding flow, marketing pages, and in-product screens.

Use this to explore a competitor's complete UI: their signup flow, pricing page, dashboard, settings, and other screens. Each screen has notes and an image URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`productId`	Yes	Product id from listProducts, e.g. linear, stripe or airbnb.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`name`	No
`tags`	No
`counts`	No
`source`	No
`screens`	No
`captured`	No
`coverage`	No
`handoffs`	No
`flowTitle`	No
`captureNote`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "captureNote": {
+      "type": "string"
+    },
+    "captured": {
+      "format": "date",
+      "type": "string"
+    },
+    "counts": {
+      "properties": {
+        "flow": {
+          "type": "integer"
+        },
+        "marketing": {
+          "type": "integer"
+        },
+        "product": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "coverage": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "flowTitle": {
+      "type": "string"
+    },
+    "handoffs": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "screens": {
+      "properties": {
+        "flow": {
+          "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"
+        },
+        "marketing": {
+          "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"
+        },
+        "product": {
+          "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"
+        }
+      },
+      "type": "object"
+    },
+    "source": {
+      "type": "string"
+    },
+    "tags": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds real value beyond them by disclosing the payload structure (grouped screens, per-screen notes and image URL). It does not mention pagination or limits, but the output schema carries return details.

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?

Two sentences, front-loaded with what is returned, then when to use it. The illustrative screen list is mildly verbose but reads as useful scoping rather than filler.

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, full parameter coverage, and safety annotations in place, the description only needed to convey scope and usage, which it does. An agent has everything required to select and call this tool.

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?

Only one parameter, fully documented in the schema (100% coverage) including an example format ('linear, stripe or airbnb'). The description adds nothing about productId, so baseline 3 is appropriate since the schema does the work.

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 a product's full collection') and enumerates the returned artifacts: coverage notes, design summary, and every captured screen grouped by category. This implicitly separates it from get_screen/get_flow (single items), but it never names a sibling tool explicitly, so differentiation requires inference.

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 this to explore a competitor's complete UI' gives clear context for when to reach for it, reinforced with concrete examples (signup flow, pricing page, dashboard, settings). There are no exclusions or named alternatives, so the agent must guess when get_design or get_screen would be preferable.

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?