Skip to main content
Glama

delete_campaign

Remove a campaign from the Keila newsletter system by specifying its ID. This action permanently deletes the campaign and its associated data.

Instructions

Delete a campaign.

Args: campaign_id: The campaign ID (e.g. "mc_12345").

Returns: Confirmation message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler that receives the request and calls the underlying client method to delete a campaign.
    def delete_campaign(campaign_id: str) -> str:
        """
        Delete a campaign.
    
        Args:
            campaign_id: The campaign ID (e.g. "mc_12345").
    
        Returns:
            Confirmation message.
        """
        _client.delete_campaign(campaign_id)
        return f"Campaign {campaign_id} deleted."
  • The actual implementation of the deletion logic, making an HTTP DELETE request to the campaign API.
    def delete_campaign(self, campaign_id: str) -> None:
        """Delete a campaign."""
        resp = self.session.delete(f"{self.url}/api/v1/campaigns/{campaign_id}", headers=self._headers(), timeout=30)
        resp.raise_for_status()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a 'Confirmation message' return value but fails to disclose critical destructive traits: whether deletion is permanent/irreversible, if it cascades to contacts/segments, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Google-style docstring format (Args/Returns) is slightly verbose for MCP but efficiently organizes information without redundant sentences. Each section serves a distinct purpose, though a more narrative style might scan better.

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?

Adequate for a single-parameter tool with an output schema, as it acknowledges the return value. However, it lacks safety warnings appropriate for a destructive operation and omits context about side effects (e.g., scheduled sends being cancelled).

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?

With 0% schema description coverage, the description fully compensates by documenting the single parameter with both semantic meaning ('The campaign ID') and a concrete example value ('mc_12345'), clarifying the expected format beyond the schema's bare type definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Delete') and resource ('campaign'), providing a clear verb-object structure. However, it does not differentiate from siblings like 'update_campaign' (which could modify vs remove) or explain the permanence of the operation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., pausing vs deleting) or prerequisites (e.g., campaign state requirements). It merely states what the tool does, not when to invoke it.

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/gwbischof/keila-mcp'

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