Skip to main content
Glama

Create an action campaign (tasks: one action in one place)

create_action_campaign

A list of concrete tasks, each ONE action in ONE place done by a community member from their own account: "post our launch in the FraCMO Slack #intros", "list us on this directory", "submit us to this newsletter". Use it when the user's buyers gather in specific communities, newsletters or directories, and a member posting there beats an ad. Read productclank://guides/action-campaign first and plan the list WITH the user. TWO STEPS: (1) call without confirmed — a FREE dry run: every task is checked (duplicate places, places in the 14-day cooldown, open tasks in communities), and you get the publish price (credits per task) and the cash deposit for usdc tasks. Show the user the list, the warnings and the price. (2) On a yes, call again with confirmed:true: the campaign is created HELD (tasks are drafts, nothing is live, nothing charged). Then: usdc tasks → give the user fund_url to deposit; then publish_action_tasks (charges credits per task).

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": {
      "title": "<title>",
      "tasks": "<tasks>"
    },
    "name": "create_action_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNoWhat the campaign is for, shown to participants
tasksYes
titleYes
space_idNoRun inside one of the user's spaces (members only). Omit for the public network.
confirmedNoLeave unset for the free dry run. true ONLY after the user agreed to the list and the price.
product_idNoFrom search_products / create_product
target_urlNoWhere each task's tracked link sends people (the product / a landing page). Default: the product's website.
duration_daysNoDefault 30
claim_ttl_hoursNoDefault hold for exclusive tasks (24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive), it discloses that the unconfirmed call is a free dry run that checks duplicates, 14-day cooldowns and open tasks, and returns price plus cash deposit. It further states that a confirmed call creates the campaign HELD with drafts and nothing charged, and that credits are charged later by publish_action_tasks — exactly the side-effect and cost disclosure an agent needs.

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?

It is front-loaded with the resource definition, then a clearly labeled 'TWO STEPS' sequence, and nearly every sentence carries either a use condition or a state/cost fact. The illustrative task quotes are slightly verbose but they do real definitional work.

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 9-parameter, money-involving mutation with no output schema, the definition covers the whole lifecycle: guide read, user planning, dry run outputs, held state, deposit URL, and the follow-up publish call. Only the exact shape of the dry-run warnings/price payload and failure modes are unspecified, which is a minor gap.

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 78%, so the baseline is 3. The description adds real meaning for the confirmed flag (unset = free dry run, true only after user agreement) but says nothing about space_id, product_id, target_url, duration_days or the nested task fields, all of which are left to the schema.

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?

The description defines the resource precisely through concrete examples ('post our launch in the FraCMO Slack #intros', 'list us on this directory') and the rule 'each ONE action in ONE place done by a community member from their own account'. That makes it distinguishable in spirit from content or ad campaigns, but it never names the sibling alternatives (create_campaign, create_content_campaign) it is not, so the agent must infer the boundary.

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?

It gives an explicit selection condition ('when the user's buyers gather in specific communities, newsletters or directories, and a member posting there beats an ad') plus procedural prerequisites: read productclank://guides/action-campaign first and plan the list WITH the user. The alternative path (publish_action_tasks) is named with its trigger, so routing is unambiguous.

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.