Skip to main content
Glama
Sign In
@kadam-net/mcp-server

@kadam-net/mcp-server

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

kadam_adv_update_creative

Update an existing ad creative by fetching its current state, merging specified changes, and sending the complete payload. Pass only the fields you want to modify; for image changes, create a new creative.

Instructions

Update an existing creative (read-modify-write). Fetches current state, merges your changes, sends full payload. Pass only the fields you want to change. For image changes, create a new creative instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "creativeId": "<creativeId>"
    },
    "name": "kadam_adv_update_creative"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidNoCustom bid for this creative
urlNoLanding page URL
textNoCreative description/text
titleNoCreative title
stopDateNoStop date (YYYY-MM-DD HH:MM:SS or null to clear)
startDateNoStart date (YYYY-MM-DD HH:MM:SS)
creativeIdYesCreative (material) ID to update
bidCountriesNoComma-separated GEO IDs for the bid
pauseAfterModerationNoPause after moderation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.9

TDQS

A4.3/5.0
Behavior4/5

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

Discloses the read-modify-write pattern, explaining that it fetches current state, merges changes, and sends full payload. No annotation contradictions; adds context beyond readOnlyHint=false.

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 concise sentences, front-loaded with operation description, followed by key usage guidance. No redundant information; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters and no output schema, the description sufficient covers behavior and key constraints (image change warning). No gaps in understanding how to use the tool.

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 parameters are well documented. The description adds only a general usage hint ('Pass only the fields you want to change'), not specific semantic details beyond the schema. Baseline of 3 is appropriate.

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?

Explicitly states 'Update an existing creative' with the read-modify-write pattern. Distinguishes from create by noting image changes require a new creative. Clearly differentiates from siblings like create_creative and set_creative_status.

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?

Provides clear guidance: 'Pass only the fields you want to change' and warns against using for image changes. Does not explicitly compare to other update tools like update_campaign, but context is adequate.

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