mcp-server

search_assets

Read-onlyIdempotent

Search RealOpen's library of approved affiliate marketing assets (flyers, social graphics, email banners, brand logos, presentations, listing media). Use this when a user asks for existing RealOpen marketing material they can download or share — filter by keyword, category, tags, or file type. Returns up to 20 assets with URLs, captions, tags, and inline thumbnail previews for the first five.

Input Schema

Name	Required	Description
`tags`	No	Filter by one or more tag slugs (assets matching ANY tag are returned)
`keyword`	No	Free-text keyword search across label and description
`category`	No	Filter by asset category
`file_type`	No	Filter by file type

Output Schema

Name	Required	Description	Default
`assets`	Yes	Up to 20 matching assets (ordered most-recent first)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / assets / items / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "assets": {
+      "description": "Up to 20 matching assets (ordered most-recent first)",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "file_type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "thumbnail_url": {
+            "description": "CDN URL for a smaller preview image",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "CDN URL for the asset itself",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "video_id": {
+            "description": "Bunny Stream video id when the asset is a video",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "label",
+          "tags"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "assets"
+  ],
+  "type": "object"
+}

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish that this is read-only, idempotent, closed-world, and non-destructive. The description adds useful behavioral detail beyond those annotations: results are capped at 20 assets and include URLs, captions, tags, and inline thumbnail previews for the first five.

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?

The description is three tightly written sentences. It front-loads the tool's purpose, then usage context, then return behavior, with no redundant or wasted language.

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 read-only search tool with four optional well-documented parameters and an output schema, the description is complete. It covers purpose, when to invoke it, filters, result cap, and response contents.

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%, and the schema already documents all four parameters with enum values and filtering semantics. The description restates the available filter dimensions but does not add meaningful syntax or behavioral details beyond the schema.

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?

The description states a specific verb and resource: searching RealOpen's approved affiliate marketing asset library, with concrete asset examples. It is clearly distinguishable from all sibling tools, which focus on wallets, account status, FAQs, and verification rather than marketing assets.

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?

It gives clear usage context: use when a user asks for existing RealOpen marketing material they can download or share. It also names the supported filtering dimensions, though it does not explicitly state when not to use the tool or compare it to alternatives.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.