Wiplash

Show Wiplash post cards

render_post_cards

Read-onlyIdempotent

Render an interactive, read-only deck for one to six public Wiplash post IDs. Call search_posts first, then pass only post IDs returned by that tool. The renderer refetches canonical public data and never executes post content.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_ids`	Yes	One to six post IDs returned by search_posts, in the display order the user requested.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`posts`	Yes
`source`	Yes
`result_count`	Yes
`untrusted_content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 17, 2026

changedOutput schema / properties / posts / items / properties / media / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "assets": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "content_type": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "filename": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "media_type": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "url": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "media_type",
-            "url",
-            "filename",
-            "content_type"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "kind": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "primary_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "urls": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "kind",
-      "primary_url",
-      "urls",
-      "assets"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "assets": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "alt": {
+              "type": "string"
+            },
+            "asset_key": {
+              "type": "string"
+            },
+            "content_type": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "filename": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "inline_svg": {
+              "type": "boolean"
+            },
+            "media_type": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "thumbnail_url": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "url": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [
+            "asset_key",
+            "media_type",
+            "url",
+            "thumbnail_url",
+            "filename",
+            "content_type",
+            "alt",
+            "inline_svg"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "kind": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "primary_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "urls": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "kind",
+      "primary_url",
+      "urls",
+      "assets"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJul 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'The renderer refetches canonical public data and never executes post content,' providing extra behavioral context beyond annotations. No contradiction.

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?

Two sentences, front-loaded with purpose, no wasted words. Every sentence adds essential information.

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?

Given the tool has one parameter, rich annotations, and an output schema, the description fully covers what the agent needs: purpose, usage flow, behavioral traits, and parameter semantics.

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% for the single parameter 'post_ids,' with a detailed description. The description adds the nuance 'in the display order the user requested,' which is not in the schema, adding value.

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 'Render an interactive, read-only deck for one to six public Wiplash post IDs,' using a specific verb and resource. It distinguishes from sibling tools like 'search_posts' and 'render_post' by specifying the range and the requirement to use IDs from search_posts.

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 description explicitly says 'Call search_posts first, then pass only post IDs returned by that tool,' providing clear when-to-use and dependency guidance. It also notes the limit of 1-6 IDs. However, it lacks explicit when-not-to-use or alternatives like using 'render_post' for a single post.

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

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