Skip to main content
Glama
Sign In

mcp-server

by io.github.realopengroup
OverviewDiscussionsAdmin

get_snippets

Read-onlyIdempotent

Find pre-approved RealOpen social-media snippets — copy-ready posts written by RealOpen's marketing team for twitter, linkedin, instagram, email, or general use. Use this when a user asks for ready-to-post content or needs inspiration grounded in approved brand voice. Filter by platform, tone, tag, attached asset, or keyword. Each snippet includes body text, tags, share title (usable as email subject), and a preview of the associated visual asset when one is attached.

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter by snippet tags (matches ANY)
toneNoFilter by snippet tone
keywordNoFree-text search on snippet text and title
asset_idNoGet snippets tied to a specific asset by ID
platformNoFilter by target platform

Output Schema

NameRequiredDescriptionDefault
snippetsYesUp to 20 matching snippets (random order to avoid stale top-matches)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / snippets / items / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "snippets": {
+      "description": "Up to 20 matching snippets (random order to avoid stale top-matches)",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "asset_file_type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "asset_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "asset_image_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "asset_label": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "platform": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "referral_url": {
+            "description": "Tracked referral URL — only present when the session has a resolved ref_id",
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "text": {
+            "description": "The actual snippet body to share",
+            "type": "string"
+          },
+          "title": {
+            "description": "Share title — usable as an email subject line",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tone": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "text",
+          "tags"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "snippets"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that snippets are pre-approved by marketing and lists the returned fields including body text, tags, share title, and asset preview, which helps set expectations without contradicting the annotations.

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?

The description is four sentences and front-loads the core definition before usage and filter details. The final sentence overlaps with the output schema's coverage of return fields, but it remains short and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations, a full input schema, and an output schema, the description covers purpose, when to use, filterable dimensions, and return contents. It does not spell out pagination or how multiple filters combine, which are minor gaps for a read-only snippet lookup.

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?

With 100% schema description coverage, the schema already defines each of the five optional filters, including enum values and the tags 'matches ANY' behavior. The description repeats the filter dimensions but adds no syntax, default, or combination semantics 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 opens with a specific verb ('Find') and a precisely scoped resource ('pre-approved RealOpen social-media snippets'), then enumerates platform contexts. It clearly distinguishes this lookup from sibling tools like search_assets by focusing on marketing snippet content rather than asset records.

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 an explicit usage trigger: 'Use this when a user asks for ready-to-post content or needs inspiration grounded in approved brand voice.' It does not name a 'do not use' case or point to an alternative tool, but the scenario is clear and actionable.

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

All mcp-server toolsInspect
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