Skip to main content
Glama
kadam-official

@kadam-net/mcp-server

Official

kadam_adv_create_creative

Create ad creatives for campaigns by specifying landing page URL and format-specific assets like images, videos, or text. Supports push, native, banner, video, and popunder formats.

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

  • Video: title, url, videoUrl (MP4)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesCampaign ID to add creative to
urlYesLanding page URL for the creative
titleNoCreative title (required for push/inpage/native/video, max 30 chars for push, 75 for native)
textNoCreative text/description (required for push/inpage, max 45 chars)
imageUrlNoIcon/image source: URL or local file path (push: 192x192+, native: 500x500+, banner: exact size)
mainImageUrlNoMain/rectangle image source: URL or local path (push/inpage: 492x328+, native: 492x328+). Not needed for banner/video.
videoUrlNoVideo source: URL or local file path to MP4 (video campaigns only)
sizeIdNoBanner size ID (required for banner). See kadam://reference/creative-formats for valid sizes.
pauseAfterModerationNoPause creative after it passes moderation (default: true for safety)
bidNoCustom bid for this creative (overrides campaign bid)
bidCountriesNoComma-separated country IDs for the bid
startDateNoCreative start date (YYYY-MM-DD HH:MM:SS)
stopDateNoCreative stop date (YYYY-MM-DD HH:MM:SS)
Behavior4/5

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

The description discloses input methods (URL/file path) and required fields per type. Annotations indicate non-read-only, which aligns. No contradictions; behavior is adequately transparent for a creation tool.

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?

Concise and well-structured: starts with main action, then general info, then per-type requirements. References external resource for details. No extraneous text.

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?

Given the tool's complexity (13 parameters, multiple types), the description covers core usage and references external documentation. Lacks details on output or error handling, but schema descriptions reduce the burden.

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

Parameters5/5

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

Schema descriptions are complete, and the description adds significant value by summarizing required fields per creative type, explaining relationships between parameters beyond what the schema provides.

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 creates a creative, specifying supported media types (image/video via URL or local file). It distinctively positions itself among siblings (create vs update/list).

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 provides detailed required fields per creative type and references external documentation for sizes. It implicitly distinguishes from update/list tools, but lacks explicit when-not-to-use guidance.

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