Skip to main content
Glama

ProductClank

by com.productclank
OverviewDiscussionsAdmin

Boost a social post

boost_post

Rally the ProductClank community to engage with a specific social post. Creates a boost campaign and spends the user's credits: 'replies' generates AI reply drafts and 'quote' generates AI-drafted QUOTE POSTS (a repost WITH each member's own text, shown above the quoted post in their followers' feeds, the highest-reach action) — both cost 20 credits per draft, 10 drafts (200 credits) by default; set count (1–10) for a smaller boost, e.g. 3 replies = 60 credits. 'likes' is 30 likes for 300 credits by default; set count (1–300) for any other size at 10 credits per like, e.g. 100 likes = 1,000 credits. 'bookmarks' (saving a post on X lifts its visibility) and 'repost' are 10 for 300 credits by default; set count (1–100) for any other size at 30 credits each, e.g. 25 reposts = 750 credits. Supports Twitter/X, Instagram, TikTok, LinkedIn, Reddit, Farcaster, and YouTube (replies + likes on YouTube; reposts only on X and Farcaster; quote posts and bookmarks only on X) — the platform is auto-detected from the URL. product_id is OPTIONAL: link a product (from search_products or create_product) to tailor replies with the product name, or omit it for a tweet-first boost that uses generic amplification language. A TikTok video under ~1 minute old has no caption yet: the boost is still created, drafts are generated once TikTok publishes the caption (usually within a few minutes), and credits are charged only then — the result says waiting_for_post_text. Pass post_text if you already know the caption to skip the wait. Delivery is immediate by default; to pace it (e.g. 'reply 3 times over the next 6 hours'), set spread_over_hours — one slot goes out now and the rest drip out 1–2 an hour so the last lands within that window, at the same price. On a TikTok / YouTube / Instagram Reel VIDEO, add watch_quiz for 'Watch & answer': viewers can also watch to the end and answer one counting question (a linked 24h watch quiz, billed 100 credits per correct answer on top of the boost price, up to max_answers — see create_watch_quiz). Confirm the action and its credit cost with the user before calling.

Input Schema

NameRequiredDescriptionDefault
countNoReplies / quote: how many drafts to generate, 1–10 (default 10), billed 20 credits per draft — 3 replies = 60 credits. Likes: how many likes, 1–300 (default 30), billed 10 credits per like — 100 likes = 1,000 credits. Repost / bookmarks: 1–100 (default 10), billed 30 credits each.
post_urlYesFull URL of the post to boost (any supported platform)
post_textNoOptional — the post's text or caption, if you already have it. Skips the server-side fetch (useful for a TikTok you just uploaded).
product_idNoOptional product UUID (from search_products or create_product). Omit for a tweet-first boost.
watch_quizNoOptional 'Watch & answer' on a TikTok / YouTube / Instagram Reel video: a linked 24h watch quiz. Billed 100 credits per correct answer (default cap 20 = 2,000 credits), separate from credits_used. Get the questions and answers from the user, or from suggest_quiz_questions.
action_typeNoHow the community engages. Default: replies. Reposts are Twitter/Farcaster only; quote posts (repost with the member's own drafted text) and bookmarks (members save the post) are X only.
reply_guidelinesNoOptional guidance for the tone and content of community replies or quote posts
spread_over_hoursNoOptional — pace delivery over this many hours instead of releasing every slot at once. One goes out now, the rest drip out 1–2 per hour. Minimum is ceil((items − 1) / 2) + 1 hours (3 items → 2, 10 → 6). Omit for immediate delivery. Same price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Replies / quote only: how many drafts to generate, 1–10 (default 10). Billed 20 credits per draft — 3 replies = 60 credits."New value: +"Replies / quote: how many drafts to generate, 1–10 (default 10), billed 20 credits per draft — 3 replies = 60 credits. Likes: how many likes, 1–300 (default 30), billed 10 credits per like — 100 likes = 1,000 credits. Repost / bookmarks: 1–100 (default 10), billed 30 credits each."
    • changedInput schema / properties / count / maximum
      Previous value: -10New value: +300
  2. Changed1 schema field changed
    • addedInput schema / properties / watch_quiz
      Added value: +{
+  "additionalProperties": false,
+  "description": "Optional 'Watch & answer' on a TikTok / YouTube / Instagram Reel video: a linked 24h watch quiz. Billed 100 credits per correct answer (default cap 20 = 2,000 credits), separate from credits_used. Get the questions and answers from the user, or from suggest_quiz_questions.",
+  "properties": {
+    "duration_sec": {
+      "anyOf": [
+        {
+          "maximum": 3600,
+          "minimum": 5,
+          "type": "integer"
+        },
+        {
+          "type": "string"
+        }
+      ],
+      "description": "Video length in seconds, or \"m:ss\". Omit to read it from the TikTok / YouTube page; other platforms need it."
+    },
+    "max_answers": {
+      "description": "People who may answer before the quiz closes to new viewers (default 20). Worst case = all of them right = 2,000 credits.",
+      "maximum": 1000,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "questions": {
+      "description": "1–20 questions with their answers. Each viewer draws one. Get them from the user — you cannot watch the video.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "answer": {
+            "description": "The whole-number answer.",
+            "minimum": 0,
+            "type": "integer"
+          },
+          "question": {
+            "description": "A counting question only someone who watched can answer, e.g. 'How many times does she say \"ship\"?'",
+            "maxLength": 200,
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "question",
+          "answer"
+        ],
+        "type": "object"
+      },
+      "maxItems": 20,
+      "minItems": 1,
+      "type": "array"
+    }
+  },
+  "required": [
+    "questions"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / action_type / description
      Previous value: -"How the community engages. Default: replies. Reposts are Twitter/Farcaster only; quote posts (repost with the member's own drafted text) are X only."New value: +"How the community engages. Default: replies. Reposts are Twitter/Farcaster only; quote posts (repost with the member's own drafted text) and bookmarks (members save the post) are X only."
    • changedInput schema / properties / action_type / enum
      Previous value: -[
-  "replies",
-  "likes",
-  "repost",
-  "quote"
-]New value: +[
+  "replies",
+  "likes",
+  "repost",
+  "quote",
+  "bookmarks"
+]
  4. Changed3 schema fields changed
    • addedInput schema / properties / count
      Added value: +{
+  "description": "Replies / quote only: how many drafts to generate, 1–10 (default 10). Billed 20 credits per draft — 3 replies = 60 credits.",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / post_text
      Added value: +{
+  "description": "Optional — the post's text or caption, if you already have it. Skips the server-side fetch (useful for a TikTok you just uploaded).",
+  "type": "string"
+}
    • addedInput schema / properties / spread_over_hours
      Added value: +{
+  "description": "Optional — pace delivery over this many hours instead of releasing every slot at once. One goes out now, the rest drip out 1–2 per hour. Minimum is ceil((items − 1) / 2) + 1 hours (3 items → 2, 10 → 6). Omit for immediate delivery. Same price.",
+  "maximum": 72,
+  "minimum": 2,
+  "type": "integer"
+}
  5. Changed3 schema fields changed
    • changedInput schema / properties / action_type / description
      Previous value: -"How the community engages. Default: replies. Reposts are Twitter/Farcaster only."New value: +"How the community engages. Default: replies. Reposts are Twitter/Farcaster only; quote posts (repost with the member's own drafted text) are X only."
    • changedInput schema / properties / action_type / enum
      Previous value: -[
-  "replies",
-  "likes",
-  "repost"
-]New value: +[
+  "replies",
+  "likes",
+  "repost",
+  "quote"
+]
    • changedInput schema / properties / reply_guidelines / description
      Previous value: -"Optional guidance for the tone and content of community replies"New value: +"Optional guidance for the tone and content of community replies or quote posts"
  6. Changed2 schema fields changed
    • changedInput schema / properties / product_id / description
      Previous value: -"Product UUID from search_products"New value: +"Optional product UUID (from search_products or create_product). Omit for a tweet-first boost."
    • changedInput schema / required
      Previous value: -[
-  "post_url",
-  "product_id"
-]New value: +[
+  "post_url"
+]
  7. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare it is non-read-only, non-destructive and open-world; the description goes far beyond that by disclosing the credit cost per action, the concrete billing math, per-platform capability limits, the TikTok caption-timing behavior and the resulting waiting_for_post_text state, and the fact that watch_quiz billing is separate from credits_used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, which is good, but the body is a single sprawling multi-clause block of em-dash-separated facts. Nearly every detail is useful in isolation, but the packaging is dense and hard to scan, so it earns only a middling score.

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 credit-spending mutation with a nested watch_quiz object and no output schema, the description covers cost, platform eligibility, pacing, deferred-charge behavior and a named result state. An agent has everything it needs to call it correctly and to warn the user about spend.

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 baseline is 3. The description largely restates the schema's own cost tables for count and repeats the platform restrictions already in action_type's enum description; only the physical explanation of a 'quote' post being the highest-reach action adds meaning beyond the structured field.

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 gives a specific verb and resource ('Creates a boost campaign'), names the concrete effect (spends the user's credits) and enumerates the distinct action types. It also references siblings (search_products, create_product, create_watch_quiz), letting an agent place it precisely in the toolset.

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 conditional guidance for choosing between action types, platform support, immediate vs paced delivery, and explicitly instructs the agent to confirm the action and cost with the user before calling. It lacks an explicit 'use this instead of create_campaign/regenerate_replies' routing statement, but the surrounding context is clear.

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

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