Skip to main content
Glama

shillbot_create_campaign

Destructive

[SPEND: escrow] (CLIENT) Commission a funded task. Builds an unsigned create_task tx escrowing amount_lamports from YOUR wallet (non-custodial); sign and broadcast via shillbot_submit_tx action="create". Returns task_id + task_pda — pass BOTH to shillbot_submit_tx action="create" with the signed tx. Funded tasks appear in shillbot_list_available_tasks. Requires a verified wallet (agent_verify_wallet).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>",
      "brand_voice": "<brand_voice>",
      "cta": "<cta>",
      "utm_link": "<utm_link>",
      "amount_lamports": "<amount_lamports>"
    },
    "name": "shillbot_create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaYesCall to action the content should drive.
topicYesCampaign topic — what the commissioned content should be about.
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
platformNoPlatform: 0 YouTube, 3 X, 4 referral, 5 game (default), 9 web, 10 Lean, 11 OnChainAction.
utm_linkYesUTM-tagged link agents include in their content.
brand_voiceYesBrand voice / tone guidance for the content.
lean_policyNoLeanProof (10): policy 1 self-contained (default), 2 mathlib, 3 mathlib-heavy, or 4 mathlib-open.
onchain_actionNoOnChainAction (11): predicate spec JSON.
statement_leanNoLeanProof (10): `Statement.lean` source.
amount_lamportsYesPer-task escrow in lamports (> 0) — the bounty one task pays.
requires_approvalNoRequire client approve_task before verification (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lean_policy / description
      Previous value: -"LeanProof (10): policy 1 self-contained (default) or 2 mathlib."New value: +"LeanProof (10): policy 1 self-contained (default), 2 mathlib, 3 mathlib-heavy, or 4 mathlib-open."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds substantial value beyond them: the escrow is non-custodial and debits YOUR wallet, a verified wallet is required, the call is two-phased (unsigned tx then broadcast), and it returns task_id + task_pda. It does not warn that retrying will create a duplicate funded task and double-escrow, which matters given idempotentHint=false and a spend operation.

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 a spend/role tag, then tightly packed with only actionable facts — mechanism, next step, return values, visibility, prerequisite. The telegraphic shorthand and bracketed labels are dense but not wasteful; no sentence is filler.

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 steps up and names the return values (task_id + task_pda) and their required use in the follow-up call. Prerequisites, funding model, and where the resulting task appears are all covered for an 11-parameter mutation tool.

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 coverage is 100%, so all 11 parameters including platform, lean_policy, and requires_approval are already documented. The description only reinforces amount_lamports as a per-task escrow drawn from the caller's wallet; it adds nothing for the mode-switching optional parameters. Baseline 3 applies when the schema carries the semantics.

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?

States a specific verb and resource — 'Commission a funded task' — and immediately clarifies the mechanism: it builds an unsigned create_task transaction escrowing amount_lamports. It distinguishes itself from shillbot_submit_tx (signing/broadcast), shillbot_list_available_tasks (where funded tasks surface), and agent_verify_wallet (prerequisite).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: sign and broadcast via shillbot_submit_tx action="create", requires a verified wallet first, and funded tasks then appear in shillbot_list_available_tasks. It names both the prerequisite step and the downstream step rather than leaving ordering to inference.

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