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_creatives

Destructive

Permanently delete archived ad creatives by passing IDs and confirm=true; archive them first with set_creative_status if needed, as unarchived or already-deleted IDs are rejected.

Instructions

Permanently delete creatives. Requires confirm=true. A creative must be archived first (use set_creative_status with status=archived), otherwise the whole call is rejected. Retrying a call that already deleted the creatives is rejected too, since deleted creatives are no longer addressable.

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": {
      "ids": "<ids>",
      "confirm": "<confirm>"
    },
    "name": "kadam_adv_delete_creatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated creative IDs
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description goes well beyond that by stating the operation is permanent, that confirm=true is mandatory, that the entire call is rejected (atomic, not partial) if archiving wasn't done, and that deleted creatives become unaddressable. These are exactly the failure modes an agent needs before committing to a destructive call.

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?

Four short sentences, front-loaded with the action and hard requirement, then prerequisites, then the retry edge case. No filler; each sentence carries a distinct operational fact.

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

Completeness5/5

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

For a two-parameter destructive tool with no output schema, the description covers the mutation semantics, the mandatory flag, the ordering prerequisite, and the rejection conditions. Nothing an agent needs before invoking it is missing.

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?

Schema coverage is 50%: 'ids' is documented in-schema as comma-separated IDs, but 'confirm' has only a const constraint and no schema description. The description compensates by explaining that confirm=true is required and that omitting it fails the call. It adds real meaning for the undocumented parameter, though it says nothing about format limits or ID count for 'ids'.

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?

States a specific verb and resource ('Permanently delete creatives') and immediately pins down scope via the confirm and archive prerequisites. An agent can distinguish it from siblings like set_creative_status, update_creative, or delete_campaigns without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-not conditions and the alternative workflow: the creative must be archived first, and it names the sibling (set_creative_status with status=archived) that accomplishes that. It also states that retries against already-deleted creatives are rejected, closing a failure path an agent would otherwise hit.

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