Skip to main content
Glama
Sign In

WowReveal

by com.wowreveal
OverviewDiscussionsAdmin

Write a post kit

create_post_kit

Write a ready-to-post kit for one platform and language: 3–5 titles, description, hashtags, first comment, hook and tips — for an existing project (project_id) or a described video (topic). Instant. Costs 1 credit(s).

Input Schema

NameRequiredDescriptionDefault
nicheNoOptional niche hint (e.g. talent show).
topicNoOr describe the video.
languageYesContent language code (list_languages): en, es, pt, fr, de, it, ru, hi, ar, bn, ur, id, fil, vi, tr, ta, te, th, ms, ja, ko, zh, pl, uk, mr, pa, sw.
platformYesTarget platform.
project_idNoUse this project's title, script and niche.
idempotency_keyNoOptional unique key (e.g. a uuid) — repeating the same call with the same key within 24 h returns the first result instead of charging again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Content language code (list_languages): en, es, pt, fr, de, it, ru, hi, ar."New value: +"Content language code (list_languages): en, es, pt, fr, de, it, ru, hi, ar, bn, ur, id, fil, vi, tr, ta, te, th, ms, ja, ko, zh, pl, uk, mr, pa, sw."
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "es",
-  "pt",
-  "fr",
-  "de",
-  "it",
-  "ru",
-  "hi",
-  "ar"
-]New value: +[
+  "en",
+  "es",
+  "pt",
+  "fr",
+  "de",
+  "it",
+  "ru",
+  "hi",
+  "ar",
+  "bn",
+  "ur",
+  "id",
+  "fil",
+  "vi",
+  "tr",
+  "ta",
+  "te",
+  "th",
+  "ms",
+  "ja",
+  "ko",
+  "zh",
+  "pl",
+  "uk",
+  "mr",
+  "pa",
+  "sw"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent). The description adds important operational context beyond annotations: it is instant and costs 1 credit, which is directly relevant to invocation decisions.

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 a single tightly packed sentence that front-loads the core action and output, with no filler. Every clause contributes useful selection or cost 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?

With no output schema, the description compensates by naming the kit contents (3–5 titles, description, hashtags, first comment, hook, tips), the input modes, platform/language scope, speed, and credit cost. That is enough for an agent to call it correctly.

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%, so the schema already documents all six parameters. The description reinforces that project_id and topic are alternative inputs and that platform/language are required, but adds no syntax or constraints beyond the structured fields.

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 ('Write a ready-to-post kit') and enumerates the deliverables (titles, description, hashtags, first comment, hook, tips), making it readily distinguishable from siblings like write_script or create_short.

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 clearly explains the two input modes: an existing project via project_id or a described video via topic, and specifies platform/language scoping. It does not explicitly name alternatives or when not to use it, so it falls short of full routing guidance.

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

All WowReveal 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