Skip to main content
Glama
JanNafta

PropellerAds MCP Server

by JanNafta

create_campaign

Create advertising campaigns on PropellerAds by specifying ad format, target countries, budget, bid model, and landing page URL.

Instructions

Create a new advertising campaign with specified settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCampaign name
ad_formatYesAd format: push, onclick, interstitial, in-page-push
countriesYesTarget country codes (e.g., ['US', 'GB', 'DE'])
daily_budgetYesDaily budget in USD
total_budgetNoTotal campaign budget in USD
bidYesBid amount (CPC/CPM)
bid_modelNoBid model: cpc, cpm, smart_cpc, smart_cpm
target_urlYesLanding page URL

Implementation Reference

  • The actual API client method that makes the POST request to create a campaign.
    def create_campaign(self, campaign_data: dict[str, Any]) -> dict[str, Any]:
        """Create a new campaign."""
        result = self._request("POST", "/adv/campaigns", json_data=campaign_data)
        return result.get("data", result) if isinstance(result, dict) else result
  • The tool handler function that parses arguments and calls the PropellerAdsClient to create a campaign.
    elif name == "create_campaign":
        campaign_data = {
            "name": args["name"],
            "ad_format": args["ad_format"],
            "countries": args["countries"],
            "daily_budget": args["daily_budget"],
            "bid": args["bid"],
            "target_url": args["target_url"],
        }
        if args.get("total_budget"):
            campaign_data["total_budget"] = args["total_budget"]
        if args.get("bid_model"):
            campaign_data["bid_model"] = args["bid_model"]
    
        result = client.create_campaign(campaign_data)
        return f"Campaign created successfully!\n\n```json\n{json.dumps(result, indent=2)}\n```"
  • The tool definition and schema registration for create_campaign.
    Tool(
        name="create_campaign",
        description="Create a new advertising campaign with specified settings.",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {"type": "string", "description": "Campaign name"},
                "ad_format": {
                    "type": "string",
                    "description": "Ad format: push, onclick, interstitial, in-page-push",
                },
                "countries": {
                    "type": "array",
                    "items": {"type": "string"},
                    "description": "Target country codes (e.g., ['US', 'GB', 'DE'])",
                },
                "daily_budget": {
                    "type": "number",
                    "description": "Daily budget in USD",
                },
                "total_budget": {
                    "type": "number",
                    "description": "Total campaign budget in USD",
                },
                "bid": {"type": "number", "description": "Bid amount (CPC/CPM)"},
                "bid_model": {
                    "type": "string",
                    "description": "Bid model: cpc, cpm, smart_cpc, smart_cpm",
                },
                "target_url": {"type": "string", "description": "Landing page URL"},
            },
            "required": ["name", "ad_format", "countries", "daily_budget", "bid", "target_url"],
        },
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation tool but doesn't mention required permissions, whether the campaign starts automatically, what happens on failure, rate limits, or what the return value contains. This leaves significant gaps for a mutation operation.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for the tool's complexity and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, error conditions, or how this differs from similar tools. The agent would need to guess about important behavioral aspects.

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%, providing good documentation for all parameters. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline for high schema coverage but doesn't enhance understanding of parameter relationships or usage patterns.

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 clearly states the action ('Create') and resource ('new advertising campaign'), making the purpose evident. However, it doesn't distinguish this tool from its sibling 'clone_campaign' or 'update_campaign', which also involve campaign creation/modification scenarios.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'clone_campaign' or 'update_campaign'. There's no mention of prerequisites, constraints, or typical use cases beyond the basic action.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JanNafta/propellerads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server