Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_create_campaign

Create a new ad campaign on Kadam network by specifying ad format, name, landing page URL, campaign group, pricing model, bid amount, daily budget, and target countries.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesAd format
nameYesCampaign name shown in dashboard
urlYesLanding page URL
folderIdYesCampaign group ID (API field: folderId)
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 list mode: whitelist (allow listed) or blacklist (block listed)
sspIdsNoComma-separated SSP IDs for the whitelist/blacklist
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,17')
frequencyCapViewsNoCreative-level cap: max views of ONE creative per user within frequencyCapDays
frequencyCapDaysNoWindow in days for frequencyCapViews
campaignCapViewsNoCampaign-level cap: max views of ANY creative from this campaign per user within campaignCapDays
campaignCapDaysNoWindow in days for campaignCapViews
impTrackerNoThird-party impression tracking pixel URL
categoriesNoComma-separated category IDs from kadam://reference/categories (or the 'mainstream'/'adult' keyword)
secondPushNoEnable second push notification (push/inpage_push only)
pauseAfterModerationNoPause campaign after creatives pass moderation
conversionTemplateIdNoConversion template ID (from campaign options). Use 0 for custom mapping via conversionApproved/Hold/Reject
conversionApprovedNoPostback status name for 'Approved' conversions (e.g. 'dep'); used with conversionTemplateId=0
conversionHoldNoPostback status name for 'Hold' conversions (e.g. 'reg')
conversionRejectNoPostback status name for 'Rejected' conversions
postViewWindowNoPost-view attribution window in hours (1-168)
postClickWindowNoPost-click attribution window in hours (1-168)
countFirstConversionOnlyNoCount only the first conversion per user (default: true)
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
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.

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