Skip to main content
Glama
Sequenzy

Sequenzy MCP Server

Official

delete_campaign

Destructive

Permanently remove a marketing campaign from your account. Active or scheduled campaigns must be cancelled before deletion.

Instructions

Permanently delete a campaign. This cannot be undone. Sending, scheduled, or paused campaigns must be cancelled with cancel_campaign first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdNoCompany ID. If not provided, uses the currently selected company.
campaignIdYesCampaign ID to delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the Sequenzy operation succeeded.
messageNoHuman-readable status, confirmation, or next-step message.
noteNoAdditional context about the result.
itemsNoFallback array wrapper used only when a tool returns a bare array.
valueNoFallback object wrapper used only when a tool returns a non-object value.
campaignIdNoDeleted campaign ID.
Behavior5/5

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

Annotations already indicate destructiveHint=true, but the description adds critical context: 'This cannot be undone' and the prerequisite to cancel active campaigns first. No contradictions with 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?

Two sentences that front-load the purpose and include essential precondition. No unnecessary words.

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?

Given the simple tool, 2 parameters, existing output schema, and annotations, the description fully covers behavior, prerequisites, and irreversibility.

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% coverage for both parameters (companyId, campaignId). The description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

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 the action ('permanently delete') and the resource ('a campaign'). It distinguishes from sibling delete tools by emphasizing permanence and linking to the related cancel_campaign tool for active campaigns.

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?

Explicitly tells when to use (to permanently delete) and when not (sending, scheduled, or paused campaigns must be cancelled first). Provides a specific alternative: cancel_campaign.

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/Sequenzy/mcp'

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