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 10 AI reply drafts (200 credits); 'quote' generates 10 AI-drafted QUOTE POSTS (200 credits) — a repost WITH each member's own text, shown above the quoted post in their followers' feeds, the highest-reach action; 'likes' (30 likes) and 'repost' (10 reposts) cost 300. Supports Twitter/X, Instagram, TikTok, LinkedIn, Reddit, Farcaster, and YouTube (replies + likes on YouTube; reposts only on X and Farcaster; quote posts 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. Confirm the action and its credit cost with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_urlYesFull URL of the post to boost (any supported platform)
product_idNoOptional product UUID (from search_products or create_product). Omit for a tweet-first boost.
action_typeNoHow the community engages. Default: replies. Reposts are Twitter/Farcaster only; quote posts (repost with the member's own drafted text) are X only.
reply_guidelinesNoOptional guidance for the tone and content of community replies or quote posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

It goes far beyond the annotations by disclosing credit costs per action, platform-specific limitations, the quote-post display mechanism, platform auto-detection, and the mandatory user-confirmation step. This is rich behavioral context for a mutating tool.

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 dense but efficient; every clause contributes operational detail. It front-loads the core purpose, then delivers costs, platform matrix, optional product behavior, and a safety instruction without fluff.

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 mutating tool with no output schema, this description covers inputs, costs, platform support, optional parameters, and user confirmation. The only minor omission is the return value, but the schema and behavioral detail are rich enough that an agent can invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema covers 100% of parameters, the description adds essential semantics: per-action credit costs, platform restrictions, optional product_id behavior, and reply_guidelines scope. This materially improves an agent's ability to choose and populate parameters correctly.

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 clearly states the specific verb-resource relationship: create a boost campaign that spends credits to drive engagement on a given social post. It distinguishes itself from content-creation and campaign-management siblings by focusing on boosting an existing post via community engagement. Platform and action-type details reinforce the tool's unique scope.

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 gives strong contextual guidance: when to link a product, when to omit it, which platforms support which actions, and the instruction to confirm cost with the user. However, it never explicitly contrasts boost_post with alternatives like create_campaign or generate_posts, so the agent must infer when to prefer this tool over siblings.

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