switch

Show Media

show_media

Read-onlyIdempotent

Display the user's images inline — one or many. Users speak plainly and will NOT know asset ids; never ask for one, resolve it yourself. For "show me" or "show me my last image" call with NO arguments (shows the most recent image). For "show me my last 4 images / my last 10 pictures" pass count=N (returns a clean grid, up to 12). For a specific known image pass assetId. Renders a branded SwitchApp media card with a Download action per result; do not just print URLs. (Videos are not shown here — use list_my_videos and return the newest finished video's view_url, which plays.)

Input Schema

Name	Required	Description	Default
`count`	No	Optional. How many of the most recent images to show as a grid (default 1, max 12). Use when the user says "my last N images/pictures".
`assetId`	No	Optional. A specific image id (from list_my_assets, search_my_library, or show_generation). Omit to show the most recent image(s).

Output Schema

Name	Required	Description	Default
`asset`	No
`images`	No
`_widget`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJun 13, 2026

changedInput schema / properties / assetId / description

Previous value: -"Asset id from list_my_assets, search_my_library, or show_generation."New value: +"Optional. A specific image id (from list_my_assets, search_my_library, or show_generation). Omit to show the most recent image(s)."

addedInput schema / properties / count

Added value: +{
+  "description": "Optional. How many of the most recent images to show as a grid (default 1, max 12). Use when the user says \"my last N images/pictures\".",
+  "type": "integer"
+}

removedInput schema / required
```
Removed value: -[
-  "assetId"
-]
```

Changed1 schema field changedJun 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "_widget": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "asset": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "images": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJun 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: it renders a branded media card with a Download action, caps the grid at 12, and instructs not to just print URLs. Return values are covered by the output schema, so this is strong but not exhaustive.

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 with the core action, then dense scenario mapping and the video exclusion. Every sentence carries distinct information, though the parenthetical video note and card-rendering clause make it slightly longer than strictly needed.

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 needn't explain return values, and it covers the remaining gaps: argument-less default, count semantics, assetId sourcing, the video exclusion, and rendering behavior. An agent has everything needed to call it correctly.

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 goes beyond the schema by giving practical semantics: count produces a grid capped at 12, and assetId must be resolved by the agent from list_my_assets/search_my_library/show_generation rather than asked of the user.

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 ("Display the user's images inline") with scope (one or many). It clearly distinguishes itself from list_my_assets, search_my_library, and show_generation by rendering rather than listing, and explicitly excludes videos in favor of list_my_videos.

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 explicit when-to-use branches: no arguments for a bare "show me," count=N for "my last N images," and assetId for a known image. It also states a when-not case (videos) and names the correct alternative tool, leaving nothing to inference.

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

All switch 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.

Resources

Need Help?