Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_create_campaign

Create a new advertiser campaign by specifying ad format, landing page URL, campaign group, pricing model, bid, daily budget, and targeted countries.

Instructions

Create a new advertiser campaign. Required: type, name, url, folderId (campaign group ID), pricingModel, bid, dailyBudget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoComma-separated OS names or IDs (e.g. 'Android,iOS' or '10,20')
bidYesBid amount in USD (e.g. 0.05). For cpa_target this is the target CPA cost
urlYesLanding page URL
nameYesCampaign name shown in dashboard
typeYesAd format
sspIdsNoComma-separated SSP IDs for the whitelist/blacklist
devicesNoComma-separated device names or IDs (e.g. 'Desktop,Smartphone' or '1,4')
endDateNoEnd date (YYYY-MM-DD)
sspModeNoSSP list mode: whitelist (allow listed) or blacklist (block listed)
browsersNoComma-separated browser names or IDs (e.g. 'Chrome,Firefox' or '8,16')
folderIdYesCampaign group ID (API field: folderId)
scheduleNoComma-separated hours (0-23) to show ads, applied to all days (e.g. '9,10,11,17')
timezoneNoTimezone offset in hours (e.g. 3 for UTC+3)
countriesYesComma-separated ISO country codes for bid targeting (e.g. 'US,DE,BR'). Required.
languagesNoComma-separated language names or IDs
startDateNoStart date (YYYY-MM-DD)
categoriesNoComma-separated category IDs from kadam://reference/categories (or the 'mainstream'/'adult' keyword)
impTrackerNoThird-party impression tracking pixel URL
secondPushNoEnable second push notification (push/inpage_push only)
dailyBudgetYesDaily spending limit in USD
totalBudgetNoTotal campaign budget in USD
pricingModelYesPricing model: cpc, cpm, or cpa_target
siteBlacklistNoComma-separated site IDs for blacklist
siteWhitelistNoComma-separated site IDs for whitelist
connectionTypeNoNetwork connection type filter (all = no filter)
conversionHoldNoPostback status name for 'Hold' conversions (e.g. 'reg')
postViewWindowNoPost-view attribution window in hours (1-168)
campaignCapDaysNoWindow in days for campaignCapViews
postClickWindowNoPost-click attribution window in hours (1-168)
campaignCapViewsNoCampaign-level cap: max views of ANY creative from this campaign per user within campaignCapDays
conversionRejectNoPostback status name for 'Rejected' conversions
evenDistributionNoSpread budget evenly across the day
frequencyCapDaysNoWindow in days for frequencyCapViews
frequencyCapViewsNoCreative-level cap: max views of ONE creative per user within frequencyCapDays
audienceExcludeIdsNoComma-separated audience IDs to exclude
audienceIncludeIdsNoComma-separated audience IDs to include
conversionApprovedNoPostback status name for 'Approved' conversions (e.g. 'dep'); used with conversionTemplateId=0
conversionTemplateIdNoConversion template ID (from campaign options). Use 0 for custom mapping via conversionApproved/Hold/Reject
pauseAfterModerationNoPause campaign after creatives pass moderation
countLastCampaignOnlyNoAttribute conversion only to the last campaign impression (default: true)
postClickAttrPriorityNoPost-click attribution takes priority over post-view (default: true)
countFirstConversionOnlyNoCount only the first conversion per user (default: true)
postConversionAudienceIdsNoComma-separated audience IDs for post-conversion retargeting

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.5.2
    • changedInput schema / properties / campaignCapDays / description
      Previous value: -"Campaign-level: time window in days (e.g. 1 = per day). Used with campaignCapViews. Example: campaignCapViews=1, campaignCapDays=1 means 'show campaign to each user max once per day'"New value: +"Window in days for campaignCapViews"
    • changedInput schema / properties / campaignCapViews / description
      Previous value: -"Campaign-level: max times ANY creative from this campaign is shown to a user within campaignCapDays (e.g. 1 = one pop per user)"New value: +"Campaign-level cap: max views of ANY creative from this campaign per user within campaignCapDays"
    • changedInput schema / properties / categories / description
      Previous value: -"Comma-separated category IDs for content classification (e.g. '1,2,3' or 'mainstream,adult'). Multiple values allowed. Use campaign options to see available IDs."New value: +"Comma-separated category IDs from kadam://reference/categories (or the 'mainstream'/'adult' keyword)"
    • changedInput schema / properties / conversionApproved / description
      Previous value: -"Postback status name for 'Approved' conversions (e.g. 'dep', 'sale'). Used with conversionTemplateId=0 for custom mapping."New value: +"Postback status name for 'Approved' conversions (e.g. 'dep'); used with conversionTemplateId=0"
    • changedInput schema / properties / conversionHold / description
      Previous value: -"Postback status name for 'Hold' conversions (e.g. 'reg', 'lead'). Used with conversionTemplateId=0 for custom mapping."New value: +"Postback status name for 'Hold' conversions (e.g. 'reg')"
    • changedInput schema / properties / conversionReject / description
      Previous value: -"Postback status name for 'Rejected' conversions. Used with conversionTemplateId=0 for custom mapping."New value: +"Postback status name for 'Rejected' conversions"
    • changedInput schema / properties / conversionTemplateId / description
      Previous value: -"Conversion acceptance template ID from campaign options (conversionTemplates list). Use 0 for custom mapping with conversionApproved/Hold/Reject."New value: +"Conversion template ID (from campaign options). Use 0 for custom mapping via conversionApproved/Hold/Reject"
    • changedInput schema / properties / countFirstConversionOnly / description
      Previous value: -"Only count the first conversion per user (default: true). Set false to allow multiple conversions per view/click"New value: +"Count only the first conversion per user (default: true)"
    • changedInput schema / properties / folderId / description
      Previous value: -"Campaign group ID (the Kadam UI calls this a 'campaign group' / 'Группа кампаний'; the API field name is folderId)"New value: +"Campaign group ID (API field: folderId)"
    • changedInput schema / properties / frequencyCapDays / description
      Previous value: -"Creative-level: time window in days for the cap (e.g. 1 = per day, 7 = per week). Used with frequencyCapViews"New value: +"Window in days for frequencyCapViews"
    • changedInput schema / properties / frequencyCapViews / description
      Previous value: -"Creative-level: max times ONE creative is shown to a user within frequencyCapDays (e.g. 3 = user sees this creative at most 3 times)"New value: +"Creative-level cap: max views of ONE creative per user within frequencyCapDays"
    • changedInput schema / properties / postClickWindow / description
      Previous value: -"Post-click attribution window in hours (1-168). Time after ad click to count a conversion"New value: +"Post-click attribution window in hours (1-168)"
    • changedInput schema / properties / postViewWindow / description
      Previous value: -"Post-view attribution window in hours (1-168). Time after ad impression to count a conversion"New value: +"Post-view attribution window in hours (1-168)"
    • changedInput schema / properties / schedule / description
      Previous value: -"Comma-separated hours (0-23) to show ads, applied to all days (e.g. '9,10,11,12,13,14,15,16,17' for 9am-5pm)"New value: +"Comma-separated hours (0-23) to show ads, applied to all days (e.g. '9,10,11,17')"
    • changedInput schema / properties / sspIds / description
      Previous value: -"Comma-separated SSP IDs for the source whitelist/blacklist (see ssps in campaign options)"New value: +"Comma-separated SSP IDs for the whitelist/blacklist"
    • changedInput schema / properties / sspMode / description
      Previous value: -"SSP source list mode: 'whitelist' = only allow listed SSPs, 'blacklist' = block listed SSPs"New value: +"SSP list mode: whitelist (allow listed) or blacklist (block listed)"
  2. Changed1 schema field changedv0.5.1
    • changedInput schema / properties / folderId / description
      Previous value: -"Campaign folder ID"New value: +"Campaign group ID (the Kadam UI calls this a 'campaign group' / 'Группа кампаний'; the API field name is folderId)"
  3. First observedv0.3.9

TDQS

A4.1/5.0
Behavior4/5

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

The description accurately indicates a mutation ('Create') which aligns with the readOnlyHint=false annotation. It doesn't describe destructive behavior or side effects, but for a creation tool, the primary action is clearly communicated. No contradictions with annotations.

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?

Two sentences, zero waste. The purpose is front-loaded and the required fields are listed succinctly. Every word earns its place.

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

Completeness3/5

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

For a complex tool with 43 parameters and no output schema, the description could mention the return value (e.g., campaign ID) or hint at optional targeting parameters. The schema covers details, but the description lacks completeness about what the agent can expect after creation.

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%, so the description adds little beyond listing required parameters. It clarifies 'folderId (campaign group ID)' which is helpful, but overall meaning is already well-covered by the schema.

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 'Create a new advertiser campaign' with a specific verb and resource, and lists required fields. It distinguishes itself from sibling tools like 'update_campaign' or 'set_campaign_status' by explicitly focusing on creation.

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 lists the required parameters, guiding the agent on what must be provided. While it doesn't explicitly mention when to use alternatives, the context of creation vs. update or deletion is clear enough for an AI agent.

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