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, name, landing page URL, folder, pricing model, bid, daily budget, and targeting options like countries, devices, and more.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesAd format
nameYesCampaign name shown in dashboard
urlYesLanding page URL
folderIdYesCampaign folder ID
pricingModelYesPricing model: cpc, cpm, or cpa_target
bidYesBid amount in USD (e.g. 0.05). For cpa_target this is the target CPA cost
dailyBudgetYesDaily spending limit in USD
countriesYesComma-separated ISO country codes for bid targeting (e.g. 'US,DE,BR'). Required.
devicesNoComma-separated device names or IDs (e.g. 'Desktop,Smartphone' or '1,4')
osNoComma-separated OS names or IDs (e.g. 'Android,iOS' or '10,20')
browsersNoComma-separated browser names or IDs (e.g. 'Chrome,Firefox' or '8,16')
languagesNoComma-separated language names or IDs
connectionTypeNoNetwork connection type filter (all = no filter)
audienceIncludeIdsNoComma-separated audience IDs to include
audienceExcludeIdsNoComma-separated audience IDs to exclude
siteWhitelistNoComma-separated site IDs for whitelist
siteBlacklistNoComma-separated site IDs for blacklist
sspModeNoSSP source list mode: 'whitelist' = only allow listed SSPs, 'blacklist' = block listed SSPs
sspIdsNoComma-separated SSP IDs for the source whitelist/blacklist (see ssps in campaign options)
totalBudgetNoTotal campaign budget in USD
evenDistributionNoSpread budget evenly across the day
startDateNoStart date (YYYY-MM-DD)
endDateNoEnd date (YYYY-MM-DD)
timezoneNoTimezone offset in hours (e.g. 3 for UTC+3)
scheduleNoComma-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)
frequencyCapViewsNoCreative-level: max times ONE creative is shown to a user within frequencyCapDays (e.g. 3 = user sees this creative at most 3 times)
frequencyCapDaysNoCreative-level: time window in days for the cap (e.g. 1 = per day, 7 = per week). Used with frequencyCapViews
campaignCapViewsNoCampaign-level: max times ANY creative from this campaign is shown to a user within campaignCapDays (e.g. 1 = one pop per user)
campaignCapDaysNoCampaign-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'
impTrackerNoThird-party impression tracking pixel URL
categoriesNoComma-separated category IDs for content classification (e.g. '1,2,3' or 'mainstream,adult'). Multiple values allowed. Use campaign options to see available IDs.
secondPushNoEnable second push notification (push/inpage_push only)
pauseAfterModerationNoPause campaign after creatives pass moderation
conversionTemplateIdNoConversion acceptance template ID from campaign options (conversionTemplates list). Use 0 for custom mapping with conversionApproved/Hold/Reject.
conversionApprovedNoPostback status name for 'Approved' conversions (e.g. 'dep', 'sale'). Used with conversionTemplateId=0 for custom mapping.
conversionHoldNoPostback status name for 'Hold' conversions (e.g. 'reg', 'lead'). Used with conversionTemplateId=0 for custom mapping.
conversionRejectNoPostback status name for 'Rejected' conversions. Used with conversionTemplateId=0 for custom mapping.
postViewWindowNoPost-view attribution window in hours (1-168). Time after ad impression to count a conversion
postClickWindowNoPost-click attribution window in hours (1-168). Time after ad click to count a conversion
countFirstConversionOnlyNoOnly count the first conversion per user (default: true). Set false to allow multiple conversions per view/click
countLastCampaignOnlyNoAttribute conversion only to the last campaign impression (default: true)
postClickAttrPriorityNoPost-click attribution takes priority over post-view (default: true)
postConversionAudienceIdsNoComma-separated audience IDs for post-conversion retargeting
Behavior3/5

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

Annotations indicate readOnlyHint=false, consistent with creation. The description does not disclose return value or side effects, but no contradiction exists.

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?

The description is concise (one sentence plus required fields list) and front-loaded, though it could include a brief example for structure.

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?

Despite the tool's complexity (43 parameters, no output schema), the description is minimal and lacks high-level context such as default post-creation state or return value.

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 no extra parameter meaning beyond the schema. Baseline 3 is appropriate.

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 the tool's action: 'Create a new advertiser campaign' and lists the required parameters, effectively distinguishing it from siblings like creating audiences or creatives.

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

Usage Guidelines3/5

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

The description implies when to use (when creating a campaign) by listing required fields, but lacks explicit guidance on when not to use or alternatives like update_campaign.

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/kadam-official/mcp-server'

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