Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_update_campaign

Update an ad campaign by passing only the fields to change. Modify targeting, budget, bid, schedule, and conversion settings with a read-modify-write approach.

Instructions

Update a campaign (read-modify-write): pass only the fields to change, same names as create. Handles all targeting/budget/bid/schedule/conversion edits. For status changes use set_campaign_status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCampaign ID to update
nameNoCampaign name shown in dashboard
urlNoLanding page URL
folderIdNoCampaign group ID (API field: folderId)
dailyBudgetNoDaily spending limit in USD
bidNoBid amount in USD. For cpa_target this is the target CPA cost
disableProxyNoBlock proxy/VPN traffic
subscriptionAgesNoComma-separated subscription-age IDs (push / in-page push only; see campaign options 'subAges'). Replaces the current set. Example: '1' = newest only.
countriesNoComma-separated ISO country codes (e.g. 'US,DE,BR')
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
Behavior5/5

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

Description explains 'read-modify-write' pattern, implying it reads current state, applies changes, and writes. Annotations have readOnlyHint=false, so the write nature is clear. No contradiction, and adds context beyond 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 front-loaded with purpose and usage guidance. No filler words; every sentence earns its place. Highly concise.

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?

With 44 parameters and no output schema, the description covers the update pattern and categories of supported edits. It doesn't mention limits or side effects, but given the complexity, it provides sufficient context for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, so baseline is 3. The description adds value by stating 'pass only the fields to change, same names as create', which clarifies the update mechanism and parameter naming consistency. This justifies a score of 4.

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?

Description states 'Update a campaign (read-modify-write)' with a specific verb and resource, and lists categories of edits (targeting/budget/bid/schedule/conversion). It distinguishes from the sibling 'set_campaign_status' for status updates.

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?

Explicitly tells when not to use this tool ('For status changes use set_campaign_status'), providing clear context. However, it does not differentiate from other update tools like 'kadam_adv_update_campaign_bid', which might cause ambiguity.

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