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_site_bids

Idempotent

Assign per-site bids to campaigns: specify a bid amount, multiplier, or use '0' to clear existing bids.

Instructions

Set per-site (zone) bids for campaigns. Bid is a number ('0.05'), a multiplier ('x1.5'), or '0' to remove.

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>",
      "zones": "<zones>",
      "bid": "<bid>"
    },
    "name": "kadam_adv_update_site_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
bidYesBid value: number ('0.05'), multiplier ('x1.5'), or '0' to remove
zonesYesComma-separated site (zone) IDs to set bids for
campaignIdsYesComma-separated campaign IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.9

TDQS

B3.3/5.0
Behavior2/5

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

Beyond the idempotentHint annotation (which already indicates safe retries), the description adds no behavioral context such as what happens if campaign or zone IDs are invalid, whether bids are overwritten or merged, or any side effects. The bid format info is parameter-related, not behavioral.

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, no fluff, front-loaded with the purpose. Every sentence adds value. It is optimally sized for quick comprehension.

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 simple update tool with three required parameters and an idempotent annotation, the description covers the core function. However, it lacks context about return values, error behavior, and differentiation from sibling tools, which limits completeness for an agent deciding between similar tools.

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?

The input schema already describes all three parameters with 100% coverage, including the bid format. The description repeats the bid format (number, multiplier, '0' to remove) but does not add new semantic information beyond the schema. Baseline 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?

The description clearly states the tool's purpose: 'Set per-site (zone) bids for campaigns.' It uses a specific verb ('set') and resource ('per-site bids'), and distinguishes from sibling tools like 'kadam_adv_update_campaign_bid' by specifying the per-site scope. The bid format explanation adds further clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus alternatives such as 'kadam_adv_bulk_update_bids' or 'kadam_adv_update_campaign_bid'. There are no explicit when-to-use or when-not-to-use instructions, nor mention of prerequisites or 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