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_create_campaign_folder

Create a new campaign group folder to organize multiple ad campaigns under a single name.

Instructions

Create a new campaign group (called 'campaign group' / 'Группа кампаний' in the Kadam UI; API term: folder).

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

Input Schema

NameRequiredDescriptionDefault
nameYesCampaign group name (1-50 characters, e.g. 'SA', 'US campaigns')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • changedInput schema / properties / name / description
      Previous value: -"Folder name (1-50 characters, e.g. 'SA', 'US campaigns')"New value: +"Campaign group name (1-50 characters, e.g. 'SA', 'US campaigns')"
  2. First observedv0.3.9

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already indicate write operation (readOnlyHint=false). Description adds terminology clarification but does not disclose behavioral traits such as uniqueness constraints, potential errors, or what happens on success (e.g., returns folder ID). The agent gains little beyond the annotation.

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 concise sentence (20 words) that directly states the purpose. No unnecessary words. Front-loaded with the key action and resource.

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?

Given a simple tool with one parameter and no output schema, the description covers the basic purpose. However, it lacks information about the expected response or side effects, which would help an agent use it correctly. The absence of output schema makes the description incomplete in terms of return value.

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 covers the single parameter (name) with a description including length and examples. The tool description adds the aliases but does not add new semantic meaning beyond the schema. With 100% schema coverage, 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?

Description clearly states the action ('Create') and resource ('campaign group' / 'folder'). It provides both UI and API terminology, and distinguishes from sibling tools like kadam_adv_create_campaign (different resource) and kadam_adv_update_campaign_folder (update vs create).

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 (when you need a new campaign group), but does not explicitly state when to use this tool vs alternatives or provide any exclusions. No prerequisites or context about when not to use it.

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