Skip to main content
Glama

Plunder & Riffle Meme Engine

Before pitch for one business

create_before_pitch

Telegram /before for ONE prospect (site, x.com/linkedin link or a sentence; never a data program's own site): Joe's welcome + five custom examples, in their site's language. campaign_id reuses a /2step's research. product pins the iMessage to a specific product/service. competitor frames the iMessage as a contrast against a named rival. deep:true crawls subpages + runs competitor-intel search before writing. Async: poll get_job_status kind demo_pack. job_id = rebuild from the same input. 50 credits ($0.50; BYOK $0.01). song_url adds a bonus song video (+30 credits). script replaces Joe's welcome script; audio_url plays a recording instead of TTS. feed:true or offer = the old text pitch: pageUrl, a 24h shareUrl with no link back, and an id for create_followup. 10 credits. feed/offer is async too: poll get_job_status kind before_text every 15-20 s.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_before_pitch"
  }
}

Input Schema

NameRequiredDescriptionDefault
deepNoDeep research: crawl subpages + search competitors.
feedNo
angleNoThe one argument Joe makes in the video (default auto: picked from the research).
inputNoWebsite, x.com / linkedin link, or a sentence about the person (max 1500 chars).
offerNoWhat the sender pitches (implies feed).
job_idNo
scriptNoYour script for the welcome video (800 characters max). Not with feed/offer.
cta_urlNohttps link the button opens, with cta_label. Default: the /options page, keeping the sender's ref. A Bankr link is not used; a t.me link becomes telegram_bot.
productNoProduct or service to feature in the iMessage.
languageNoWrite and speak the pitch in this language (default: their site's).
song_urlNohttps song link: bonus song video, +30 credits, shown as a sixth phone. Not with feed/offer.
audio_urlNohttps mp3/wav/m4a played instead of TTS. Not with feed/offer.
cta_labelNoButton words (40 characters max), with cta_url. Default: SEE YOUR OPTIONS →.
competitorNoCompetitor or rival to contrast against in the iMessage.
campaign_idNo
video_styleNo
telegram_botNoTheir Telegram bot (@name or t.me link): its own button, "Chat with @name on Telegram", under the main one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only supply destructiveHint=false, but the description discloses a great deal beyond them: async execution with polling via get_job_status kind demo_pack, a 15-20s poll cadence for feed mode, job_id rebuild semantics, credit costs (50 credits/$0.50, BYOK $0.01, +30 for song_url, 10 for feed), and that the feed shareUrl expires in 24h with no link back.

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?

Front-loaded with purpose and scope, then telegraphic one-clause-per-feature sentences so each clause carries distinct information (modes, credits, async behavior). It is dense and jargon-heavy, which costs readability, but there is little filler given the breadth of behavior it must convey.

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?

For a 17-parameter, no-output-schema, async job tool, the description covers invocation, cost, polling, and the two output modes (demo pack vs. pageUrl/shareUrl/id for create_followup). What is thinner is the exact shape of the demo-pack result and default values for several optional params, though those defaults mostly live in the schema.

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 76%, so the schema already documents most parameters, yet the description adds meaning where it is missing: campaign_id ties to a /2step's research, job_id rebuilds from identical input, and feed/offer trigger the legacy text-pitch mode. It also clarifies the cta_url default (the /options page keeping the sender's ref) beyond the schema's wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb+resource: creates a 'Telegram /before' pitch for ONE prospect from a site, x.com/linkedin link, or a sentence, and states what it produces ('Joe's welcome + five custom examples, in their site's language'). The 'ONE prospect (never a data program's own site)' scoping separates it from bulk flows, though internal jargon like 'Joe's welcome' and '/before' assumes prior product knowledge.

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?

Gives clear when-to-use context and mode selection: use deep:true to crawl subpages and run competitor-intel search, campaign_id to reuse a /2step's research, feed:true or offer for the older text pitch at 10 credits. It does not explicitly route to sibling creation tools like create_before_scroll or create_whiteboard_pitch, so alternatives are only partly covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources