Skip to main content
Glama
bcharleson

Instantly MCP Server

get_campaign

Read-only

Retrieve detailed campaign information including sequences, schedules, sender accounts, tracking settings, and status statistics from the Instantly.ai email outreach platform.

Instructions

Get campaign details: config, sequences, schedules, sender accounts, tracking, status.

Returns comprehensive campaign information including:

  • Email sequences and their content

  • Schedule configuration

  • Sender account assignments

  • Tracking settings (opens, clicks)

  • Campaign status and statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main execution handler for the 'get_campaign' tool. Fetches detailed campaign information from the Instantly API using the provided campaign_id and returns it as formatted JSON.
    async def get_campaign(params: GetCampaignInput) -> str:
        """
        Get campaign details: config, sequences, schedules, sender accounts, tracking, status.
        
        Returns comprehensive campaign information including:
        - Email sequences and their content
        - Schedule configuration
        - Sender account assignments
        - Tracking settings (opens, clicks)
        - Campaign status and statistics
        """
        client = get_client()
        result = await client.get(f"/campaigns/{params.campaign_id}")
        return json.dumps(result, indent=2)
  • Pydantic input schema for the get_campaign tool, defining the required 'campaign_id' parameter.
    class GetCampaignInput(BaseModel):
        """Input for getting campaign details."""
        
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
        
        campaign_id: str = Field(..., description="Campaign UUID")
  • MCP tool registration annotation specifying that 'get_campaign' is read-only.
    "get_campaign": {"readOnlyHint": True},
  • The CAMPAIGN_TOOLS list that includes the get_campaign function, used by the server for tool collection and registration.
    CAMPAIGN_TOOLS = [
        create_campaign,
        list_campaigns,
        get_campaign,
        update_campaign,
        activate_campaign,
        pause_campaign,
        delete_campaign,
        search_campaigns_by_contact,
    ]
Behavior4/5

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

The annotations provide readOnlyHint=true, which the description aligns with by describing a retrieval operation ('Get campaign details'). The description adds valuable behavioral context beyond annotations by specifying what comprehensive information is returned (email sequences, schedule configuration, sender accounts, tracking settings, status/statistics), which helps the agent understand the scope and format of returned data.

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 is efficiently structured with a clear opening sentence stating the purpose, followed by a bulleted list detailing returned information. Every sentence earns its place by adding specific value about what the tool returns, with no redundant or vague phrasing.

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 tool's moderate complexity (retrieving detailed campaign data), the description provides good context about what information is returned. With annotations covering read-only safety and an output schema presumably detailing the response structure, the description focuses appropriately on clarifying the scope of returned data without needing to explain return values or safety aspects.

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 schema only states 'Input for getting campaign details' and 'Campaign UUID'), the description compensates well by implicitly clarifying that campaign_id is required to fetch details for a specific campaign. While it doesn't explicitly mention the parameter, the context makes its purpose clear. For a single parameter tool, this provides adequate semantic understanding.

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 tool's purpose as retrieving campaign details with specific components listed (config, sequences, schedules, sender accounts, tracking, status). It distinguishes from siblings like list_campaigns (which lists campaigns) and update_campaign (which modifies campaigns), but doesn't explicitly contrast with get_account or get_lead which have similar 'get' patterns for different resources.

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?

Usage is implied by the description's focus on retrieving comprehensive details for a specific campaign, suggesting it should be used when detailed information is needed rather than just listing campaigns. However, there's no explicit guidance on when to use this versus alternatives like search_campaigns_by_contact or what prerequisites exist (e.g., needing a valid campaign_id).

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/bcharleson/instantly-mcp-python'

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