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_extended_bids

Update per-slice bids for campaigns: set fixed or multiplier bids, blacklist, un-blacklist, or remove bids using pathIds from extended stats.

Instructions

Set / multiply / blacklist / remove per-slice bids (Bid Optimization). Bulk: every bid op applies to all listed campaigns. action: set (needs mode+bid), off (blacklist), on (un-blacklist), remove (delete). Get pathIds from kadam_adv_get_extended_stats.

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": {
      "campaignIds": "<campaignIds>",
      "bids": "<bids>"
    },
    "name": "kadam_adv_update_extended_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidsYes
campaignIdsYesComma-separated campaign IDs (CPC/CPM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.4

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate write behavior (readOnlyHint=false). The description adds behavioral details about actions and bulk application, but does not cover error states, idempotency, or response structure. No contradiction with 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?

The description is three concise sentences, front-loaded with key information, and every sentence adds value without fluff.

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?

The tool lacks an output schema, so the description should cover response expectations. It covers main functionality and required IDs but omits details on success/failure, idempotency, and invalid inputs.

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?

The description adds meaning beyond schema by explaining action values ('off' = blacklist, 'on' = un-blacklist) and noting the source of pathIds. Given schema description coverage of 50%, the description significantly compensates.

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 sets/multiplies/blacklists/removes per-slice bids with strong verbs and specific resource. It distinguishes from sibling tools like kadam_adv_bulk_update_bids by focusing on 'extended' and 'per-slice' bids.

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 context that operations apply to all listed campaigns and directs to another tool for obtaining pathIds. It lacks explicit when-not-to-use guidance but offers clear usage context.

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