Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

campaign_bulk_delete_catalog_ad_items

Bulk delete catalog ad items from a campaign using campaign ID and item IDs. This removes unwanted items in one operation, simplifying campaign management.

Instructions

Bulk delete catalog ad items from a campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesArray of catalog ad item IDs to delete
campaign_idYesCampaign ID
Behavior2/5

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

No annotations provided; description labels destructive action without disclosing irreversibility, partial failure behavior, or permission requirements. For a bulk delete operation, this is a significant gap.

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?

Single sentence, zero redundancy. Every word contributes to meaning.

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 tool is simple with fully described params, but missing details on return value, atomicity, and error handling for invalid IDs. No output schema exists, so description should provide more operational context for a destructive bulk operation.

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?

Input schema has 100% description coverage, so baseline 3 applies. The description adds no additional meaning beyond schema fields, and the schema already documents items array and campaign_id.

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 uses specific verb 'Bulk delete' and resource 'catalog ad items from a campaign', clearly distinguishing from sibling campaign_bulk_create_catalog_ad_items and single delete_catalog_ad_item. The scope 'from a campaign' is precise.

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 word 'bulk' implies use for multiple items, but no explicit guidance on when to use this over single delete_catalog_ad_item or draft_delete_catalog_ad_item. No exclusions or alternatives named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adbutler/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server