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_delete_audience

Destructive

Permanently delete an audience from your ad network. Confirmation is mandatory to prevent accidental removal.

Instructions

Permanently delete an audience. Requires confirm=true for safety.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "kadam_adv_delete_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.9

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already set destructiveHint=true, and the description adds the detail that deletion is permanent and requires confirm=true. This adds non-obvious behavioral context beyond 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 sentence conveying critical information with no wasted words. It is appropriately short and front-loaded.

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

Completeness4/5

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

For a simple delete tool with two parameters and no output schema, the description covers the key safety requirement and permanence. It does not describe return values, but that is acceptable given the action's nature.

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 0%, so the description must compensate. It explains the purpose of confirm (safety) but does not describe the id parameter. This provides partial but not complete parameter guidance.

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 'Permanently delete an audience', which is a specific verb (delete) and resource (audience). It distinguishes from sibling tools like create_audience or update_audience.

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 the explicit guideline 'Requires confirm=true for safety', indicating the required parameter setting. It does not elaborate on when not to use, but for a delete operation, this 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