Skip to main content
Glama

get_campaign

Fetch detailed information about a specific newsletter campaign by providing its ID, including subject, content, sender details, target segment, and delivery status.

Instructions

Fetch a single campaign by ID.

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

Returns: Campaign details including subject, body, sender, segment, and delivery status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Implementation Reference

  • The MCP tool definition for `get_campaign` which serves as the entry point and registers the tool.
    @mcp.tool()
    def get_campaign(campaign_id: str) -> dict:
        """
        Fetch a single campaign by ID.
    
        Args:
            campaign_id: The campaign ID (e.g. "mc_12345").
    
        Returns:
            Campaign details including subject, body, sender, segment, and delivery status.
        """
        return _client.get_campaign(campaign_id)
  • The actual implementation of `get_campaign` in the `KeilaClient` class, which makes the HTTP request to the Keila API.
    def get_campaign(self, campaign_id: str) -> dict:
        """Fetch a single campaign by ID."""
        resp = self.session.get(f"{self.url}/api/v1/campaigns/{campaign_id}", headers=self._headers(), timeout=30)
        resp.raise_for_status()
        return resp.json()
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It adds valuable behavioral context by detailing the return value structure ('subject, body, sender, segment, and delivery status'), but omits safety characteristics (read-only implied by 'Fetch' but not stated), error conditions, or authentication requirements.

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 docstring-style structure (Args/Returns) is clear and front-loaded with the main purpose. Every sentence earns its place; however, the formatting is slightly mechanical and could be more integrated as prose.

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?

Given the low complexity (one string parameter, no nested objects) and lack of output schema, the description provides adequate completeness by documenting both the input parameter (with example) and the expected return values.

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 compensates by documenting the parameter in the Args section and providing a concrete format example ('mc_12345'), which adds essential semantic meaning missing from the schema.

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 states the specific action ('Fetch'), resource ('campaign'), and scope ('single campaign by ID'). It implicitly distinguishes from sibling 'list_campaigns' by emphasizing 'single', though it does not explicitly name siblings.

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 description implies usage ('by ID') suggesting it should be used when a specific campaign identifier is known, but provides no explicit guidance on when to prefer this over 'list_campaigns' or other campaign-related tools.

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