Skip to main content
Glama

sequence_create

Create automated outreach campaigns with timed email sequences and multi-channel steps for sales prospecting and follow-up workflows.

Instructions

    Create a new email sequence with steps.

    This is a powerful tool for creating automated outreach campaigns.

    Args:
        name: Sequence name
        steps: List of step configurations. Each step should have:
            - type: "auto_email", "manual_email", "phone_call", "action_item",
                    "linkedin_connection", "linkedin_message", "linkedin_view", "linkedin_interact"
            - wait_time: Time to wait before this step (integer)
            - wait_mode: "minute", "hour", or "day"
            - For email steps, include emailer_touches with:
                - type: "new_thread" or "reply"
                - subject: Email subject (supports {{variables}})
                - body_html: Email body HTML (supports {{variables}})
        schedule_id: Optional sending schedule ID
        active: Whether to activate immediately

    Returns:
        Created sequence details

    Example:
        sequence_create(
            name="New Outreach Campaign",
            steps=[
                {
                    "type": "auto_email",
                    "wait_time": 0,
                    "wait_mode": "minute",
                    "emailer_touches": [{
                        "type": "new_thread",
                        "subject": "Quick question about {{company}}",
                        "body_html": "<p>Hi {{first_name}},</p><p>I noticed {{company}} is growing...</p>"
                    }]
                },
                {
                    "type": "auto_email",
                    "wait_time": 3,
                    "wait_mode": "day",
                    "emailer_touches": [{
                        "type": "reply",
                        "subject": "Re: Quick question about {{company}}",
                        "body_html": "<p>Following up on my last email...</p>"
                    }]
                }
            ]
        )

    Available variables: {{first_name}}, {{last_name}}, {{company}}, {{title}},
                        {{email}}, {{phone}}, {{city}}, {{state}}, {{country}}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
stepsYes
schedule_idNo
activeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that this is a 'powerful tool for creating automated outreach campaigns' (implying mutation), describes the return value ('Created sequence details'), and provides a comprehensive example. However, it doesn't mention permissions, rate limits, or error conditions.

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 description is appropriately sized and front-loaded with the core purpose. The example and variable list are valuable but make it slightly longer. Every section (purpose, args, returns, example, variables) earns its place by adding necessary information.

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 complexity (4 parameters with nested structures, 0% schema coverage, no annotations) and the presence of an output schema, the description is complete. It covers purpose, detailed parameter semantics, return values, an illustrative example, and available variables—providing everything needed for correct tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 detailing all 4 parameters. It explains 'name' and 'steps' thoroughly (including nested configurations for step types, wait times, and emailer_touches), clarifies optionality of 'schedule_id', and specifies default behavior for 'active'. The example and variable list add further clarity.

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 verb ('create') and resource ('new email sequence with steps'), distinguishing it from siblings like sequence_get, sequences_list, or sequence_activate. It specifies this is for 'automated outreach campaigns,' which helps differentiate from other creation tools like deal_create or workflow_create.

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 for 'automated outreach campaigns' but doesn't explicitly state when to use this tool versus alternatives like workflow_create or email_send. No guidance on prerequisites, exclusions, or specific scenarios where this tool is preferred over siblings is provided.

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/BlockchainRev/apollo-mcp-server'

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