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_list_extended_bids

Read-only

List the per-slice bid overrides set on campaigns for bid optimization. Supports pagination by page number and per-page count.

Instructions

List the per-slice bid overrides currently set on campaign(s) (Bid Optimization). Paginated.

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>"
    },
    "name": "kadam_adv_list_extended_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
perPageNo
campaignIdsYesComma-separated campaign IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds that the tool is paginated and lists 'per-slice bid overrides' under 'Bid Optimization', which provides slight behavioral context but no additional safety or auth details. 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 a single, efficient sentence that front-loads the action and resource. No wasted words.

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 description mentions listing and pagination but does not describe the output format or structure. Given no output schema, this omission reduces completeness for an agent to understand what to expect.

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

Parameters2/5

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

Schema description coverage is 33% (only 'campaignIds' has a description). The description does not explain any parameters beyond implying campaignIds are needed. It adds no meaning to 'page' or 'perPage' 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 verb 'List', the resource 'per-slice bid overrides', and the context 'Bid Optimization'. This uniquely identifies the tool's function and distinguishes it from siblings like 'kadam_adv_bulk_update_bids' and 'kadam_adv_update_extended_bids'.

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

Usage Guidelines3/5

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

The description implies usage for reading bid overrides but provides no explicit guidance on when to use this tool versus other listing tools (e.g., 'kadam_adv_list_campaigns'). No when-not or alternative tools are mentioned.

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