Skip to main content
Glama

list_campaigns

Retrieve all newsletter campaigns from Keila to view subjects, schedules, and statuses for managing email marketing efforts.

Instructions

List all campaigns in Keila.

Returns: A dict with 'data' (list of campaigns). Each campaign has id, subject, text_body, sender_id, segment_id, settings, sent_at, scheduled_for, and timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the campaign list retrieval via the API client.
    def list_campaigns(self) -> dict:
        """List all campaigns."""
        resp = self.session.get(f"{self.url}/api/v1/campaigns", headers=self._headers(), timeout=30)
        resp.raise_for_status()
        return resp.json()
  • mcp_server.py:99-108 (registration)
    The MCP tool registration and wrapper that calls the client's list_campaigns method.
    @mcp.tool()
    def list_campaigns() -> dict:
        """
        List all campaigns in Keila.
    
        Returns:
            A dict with 'data' (list of campaigns). Each campaign has id, subject,
            text_body, sender_id, segment_id, settings, sent_at, scheduled_for, and timestamps.
        """
        return _client.list_campaigns()
Behavior3/5

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

No annotations provided, so description carries full burden. Compensates by detailing return structure (dict with 'data' containing campaign objects with specific fields), which is helpful. However, missing operational details like pagination behavior, result limits, or whether deleted/draft campaigns are included.

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?

Two-section structure is appropriate: clear action statement followed by Returns documentation. The Returns section is necessary given lack of output schema. No redundant or filler text, though 'in Keila' could be assumed from context.

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?

Describes return structure adequately compensating for missing output schema. However, given the many sibling tools available, lacks contextual guidance for proper tool selection and doesn't address scale concerns (how many is 'all'?).

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?

Input schema has 0 parameters with 100% coverage (empty object). Description correctly offers no parameter semantics since none exist to describe. Baseline applies.

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?

States 'List all campaigns in Keila' with clear verb and resource scope. However, lacks explicit distinction from sibling get_campaign (single retrieval) or mention that this returns unfiltered complete lists.

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?

No explicit when-to-use guidance, prerequisites, or alternatives. Doesn't advise when to use this versus get_campaign, or warn about potential performance implications of listing all campaigns.

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