Skip to main content
Glama
pauloFroes

mcp-meta-marketing

by pauloFroes

Delete Campaign

delete_campaign
Destructive

Delete a campaign irreversibly. Consider archiving to keep the campaign data.

Instructions

Delete a campaign. This is irreversible. Consider using update_campaign with status=ARCHIVED instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign ID to delete
Behavior4/5

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

Annotations already indicate destructiveHint: true and readOnlyHint: false, so the description doesn't need to repeat those. It adds the key nuance that deletion is 'irreversible,' which goes beyond the annotation by clarifying permanence. This is helpful and adds value without contradicting any 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 consists of three short sentences, each carrying essential information: the action, irreversibility, and an alternative. It is front-loaded with the primary verb and resource and contains no filler or redundancy.

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 one-parameter delete tool with no output schema, the description adequately covers purpose, irreversibility, and alternatives. It doesn't mention any potential cascade effects or required permissions, but given the simplicity and the annotations, it is nearly complete.

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?

The input schema has 100% description coverage for the single parameter campaign_id, with the field clearly described as 'Campaign ID to delete.' The description adds no further parameter detail, and since schema coverage is complete, the baseline of 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?

The description opens with 'Delete a campaign,' which clearly specifies the verb and resource, matching the tool name exactly. It also distinguishes from sibling delete tools like delete_adset and delete_ad, and from update_campaign, which is explicitly mentioned as an alternative.

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 suggests 'Consider using update_campaign with status=ARCHIVED instead,' providing an explicit alternative for reversible deletion. However, it doesn't explicitly state the exact conditions under which delete_campaign should be chosen (e.g., 'use when permanent deletion is required'), leaving some implied context.

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/pauloFroes/mcp-meta-marketing'

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