Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_update_campaign

Update a campaign by providing only the fields you want to change. The tool reads the current state, merges your changes, and submits the full campaign payload.

Instructions

Update an existing campaign (read-modify-write). Fetches current state, merges your changes, sends full payload. Pass only the fields you want to change. Uses same field names as create. For status changes use set_campaign_status instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCampaign ID to update
nameNoCampaign name shown in dashboard
urlNoLanding page URL
folderIdNoCampaign folder ID
dailyBudgetNoDaily spending limit in USD
bidNoBid amount in USD. For cpa_target this is the target CPA cost
disableProxyNoBlock proxy/VPN traffic
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 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
Behavior4/5

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

The description discloses the read-modify-write pattern: 'Fetches current state, merges your changes, sends full payload.' This adds value beyond the minimal annotations (readOnlyHint: false). No contradiction found. Could optionally mention idempotency or side effects.

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 extremely concise: two sentences front-load the core purpose and merge behavior. No unnecessary words or repetition.

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 explains the update mechanism well but omits what the response contains (e.g., updated campaign object). It references sibling tools for context, which is helpful, but missing output info lowers completeness.

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?

With 100% schema coverage, the parameter descriptions in JSON Schema are already detailed. The description adds little beyond noting that field names match the create tool. Baseline of 3 is appropriate as no significant additional semantics are provided.

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 'Update an existing campaign (read-modify-write)' and distinguishes itself from sibling tools like 'set_campaign_status' (for status changes) and 'update_campaign_bid' (for bid updates). The verb 'update' and resource 'campaign' are specific.

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 advises to 'Pass only the fields you want to change' and directs status changes to 'set_campaign_status'. It provides context on when to use this tool, though it does not explicitly mention alternatives for bid-only updates or bulk operations.

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