Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official
by kadam-official
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

kadam_adv_create_creative

Create a new ad creative for a campaign by supplying a landing page URL and format-specific media such as images, video, or HTML5 archives.

Instructions

Create a creative. Accepts image/video as a URL or local file path. Required fields by type:

  • Push / In-Page Push: title, text, url, imageUrl (icon), mainImageUrl

  • Native: title, url, imageUrl (icon), mainImageUrl

  • Banner: url, imageUrl, sizeId

  • Banner as an HTML5 archive: url, html5ArchiveUrl (.zip), sizeId — needs the HTML5 grant

  • Video: title, url, videoUrl (MP4) — uploading a video file is an internal grant; advertisers deliver video as a VAST tag

  • Video as a VAST tag: title, vastTagUrl (https) in a video campaign — needs the VAST grant, nothing is uploaded

  • Popunder: none (campaign URL is the ad) See kadam://reference/creative-formats for sizes and exact dimensions.

Input Schema

NameRequiredDescriptionDefault
bidNoCustom bid for this creative (overrides campaign bid)
urlYesLanding page URL for the creative
textNoCreative text/description (required for push/inpage, max 45 chars)
titleNoCreative title (required for push/inpage/native/video, max 30 chars for push, 75 for native)
sizeIdNoBanner size ID (required for banner). See kadam://reference/creative-formats for valid sizes.
imageUrlNoIcon/image source: URL or local file path (push: 192x192+, native: 500x500+, banner: exact size)
stopDateNoCreative stop date (YYYY-MM-DD HH:MM:SS)
videoUrlNoVideo source: URL or local file path to MP4 (video campaigns only)
startDateNoCreative start date (YYYY-MM-DD HH:MM:SS)
campaignIdYesCampaign ID to add creative to
vastTagUrlNohttps VAST tag URL (video campaigns only). The tag is fetched and parsed on save, so a tag that does not answer with a usable VAST document is refused right away.
bidCountriesNoComma-separated country IDs for the bid
mainImageUrlNoMain/rectangle image source: URL or local path (push/inpage: 492x328+, native: 492x328+). Not needed for banner/video.
html5ArchiveUrlNoHTML5 archive (.zip): URL or local file path (banner campaigns only)
pauseAfterModerationNoPause creative after it passes moderation (default: true for safety)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.1
    • addedInput schema / properties / html5ArchiveUrl
      Added value: +{
+  "description": "HTML5 archive (.zip): URL or local file path (banner campaigns only)",
+  "type": "string"
+}
    • addedInput schema / properties / vastTagUrl
      Added value: +{
+  "description": "https VAST tag URL (video campaigns only). The tag is fetched and parsed on save, so a tag that does not answer with a usable VAST document is refused right away.",
+  "type": "string"
+}
  2. First observedv0.3.9

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the single readOnlyHint=false annotation: it discloses that HTML5 and video uploads require internal grants, that advertisers normally deliver video as a VAST tag with nothing uploaded, that the VAST tag is fetched and parsed on save and rejected if no usable document is returned, and that pauseAfterModeration defaults to true for safety.

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?

Front-loads the verb and resource in one line, then uses a tight scannable bullet list keyed by creative type, ending with a pointer to the reference resource for sizes. No filler sentences; every line carries actionable information.

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?

For a 15-parameter, no-output-schema creation tool, the description covers format requirements, grants, and the moderation/pause default, which is what an agent needs to invoke it correctly. Minor gaps remain: no statement of what the created creative's initial status is beyond the pause flag, and no mention of how it relates to bulk creation.

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 description coverage is already 100%, so the baseline is 3, but the description adds real value by consolidating requirements into a per-format matrix (e.g., Banner = url + imageUrl + sizeId; Video = title + url + videoUrl) that is not derivable from reading individual property descriptions in isolation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a creative') and immediately enumerates the format-specific required fields, so the agent knows exactly what this operation produces. It does not, however, reference the adjacent 'create_bulk_creatives' sibling, so the single-vs-bulk distinction must be inferred.

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 per-type requirement list effectively tells the agent when each field combination applies (Push, Native, Banner, HTML5, Video, VAST, Popunder) and flags grant prerequisites for HTML5 archive and VAST/video upload. It gives no explicit exclusions or named alternatives (e.g., when to prefer bulk creation or update_creative).

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

Deploy Server

Other Tools