Skip to main content
Glama
revenue-enablement-mcp

revenue-enablement-mcp

Email Sequence Generator

email_sequence_generator
Read-only

Generate scheduled outreach email sequences with subjects, send days, and bodies from your persona, stage, and objective. Build cold, follow-up, or re-engagement emails with no invented stats or placeholders.

Instructions

Helps you decide what to send, and when, to open or restart a conversation. You give the persona, stage and objective (prospecting, nurture, follow up or re engagement), plus your solution, the pain point, value proposition, proof and ask. You get each email with its subject, send day and body, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of sales_enablement_content when you need scheduled outreach emails with subjects and send days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sequence_type": "<sequence_type>",
      "target_persona": "<target_persona>",
      "your_solution": "<your_solution>"
    },
    "name": "email_sequence_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoEmail tone. Format is text using one of the listed labels. For example, "professional".
num_emailsNoAccepted but not used yet: each sequence type has a fixed number of emails. Format is a JSON number. For example, 12.
your_sectorNoOptional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech".
social_proofNoCustomer names, stats, or proof points. Format is text. For example, "Company-reported pilot reduced approval time from 12 to 9 days in October 2026.".
sequence_typeYesType of email sequence. cold_outreach, warm_follow_up, post_demo and re_engagement have their own templates; the other types return a general outline. Format is text using one of the listed labels. For example, "cold_outreach".
your_solutionYesYour product/solution. Format is text. For example, "invoice review service".
call_to_actionNoDesired action (meeting, demo, reply). Format is text. For example, "book a discovery call".
key_value_propNoPrimary value proposition. Format is text. For example, "resolve invoice exceptions before month-end".
sender_contextNoContext about sender (role, shared connections, etc.). Format is text. For example, "account owner following up after discovery".
target_personaYesTarget persona (e.g., VP Sales, CTO, CFO). Format is text.
target_industryNoTarget industry for context. Format is text. For example, "manufacturing".
specific_pain_pointNoSpecific pain point to address. Format is text. For example, "invoice exceptions delay month-end close".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.2.33
    • changedInput schema / properties / call_to_action / description
      Previous value: -"Desired action (meeting, demo, reply)"New value: +"Desired action (meeting, demo, reply). Format is text. For example, \"book a discovery call\"."
    • changedInput schema / properties / key_value_prop / description
      Previous value: -"Primary value proposition"New value: +"Primary value proposition. Format is text. For example, \"resolve invoice exceptions before month-end\"."
    • changedInput schema / properties / num_emails / description
      Previous value: -"Number of emails in sequence (3-7)"New value: +"Accepted but not used yet: each sequence type has a fixed number of emails. Format is a JSON number. For example, 12."
    • addedInput schema / properties / num_emails / minimum
      Added value: +0
    • changedInput schema / properties / sender_context / description
      Previous value: -"Context about sender (role, shared connections, etc.)"New value: +"Context about sender (role, shared connections, etc.). Format is text. For example, \"account owner following up after discovery\"."
    • changedInput schema / properties / sequence_type / description
      Previous value: -"Type of email sequence"New value: +"Type of email sequence. cold_outreach, warm_follow_up, post_demo and re_engagement have their own templates; the other types return a general outline. Format is text using one of the listed labels. For example, \"cold_outreach\"."
    • changedInput schema / properties / social_proof / description
      Previous value: -"Customer names, stats, or proof points"New value: +"Customer names, stats, or proof points. Format is text. For example, \"Company-reported pilot reduced approval time from 12 to 9 days in October 2026.\"."
    • changedInput schema / properties / specific_pain_point / description
      Previous value: -"Specific pain point to address"New value: +"Specific pain point to address. Format is text. For example, \"invoice exceptions delay month-end close\"."
    • changedInput schema / properties / target_industry / description
      Previous value: -"Target industry for context"New value: +"Target industry for context. Format is text. For example, \"manufacturing\"."
    • changedInput schema / properties / target_persona / description
      Previous value: -"Target persona (e.g., VP Sales, CTO, CFO)"New value: +"Target persona (e.g., VP Sales, CTO, CFO). Format is text."
    • changedInput schema / properties / tone / description
      Previous value: -"Email tone"New value: +"Email tone. Format is text using one of the listed labels. For example, \"professional\"."
    • addedInput schema / properties / your_sector
      Added value: +{
      +  "description": "Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, \"logistics_tech\".",
      +  "enum": [
      +    "logistics_tech",
      +    "fintech",
      +    "saas",
      +    "vertical_saas",
      +    "ai_native",
      +    "ites",
      +    "telecom",
      +    "software",
      +    "cybersecurity",
      +    "other"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / your_solution / description
      Previous value: -"Your product/solution"New value: +"Your product/solution. Format is text. For example, \"invoice review service\"."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses that no sign-in is needed, no inputs or outputs are stored, and hosted usage metadata is recorded — privacy-relevant facts an agent cannot get from annotations. It also states output guarantees (no unresolved placeholders, no invented statistics, a note on what was omitted) and defines the error behavior for missing or invalid fields.

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?

It is dense but nearly every sentence carries new information: purpose, inputs, outputs, guarantees, storage behavior, error behavior, alternative tool. The order is sensible, though the sibling-routing sentence sits last where it would be more useful earlier, and the prose is one long unbroken block.

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?

For a 12-parameter, no-output-schema tool, the description covers outputs, error behavior, auth/storage, and tool choice well. Minor gaps remain: it does not mention that sequences are fixed-length per type (num_emails is effectively ignored) or how tone alters the output, both discoverable only in the schema.

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?

Schema coverage is 100%, so the schema already documents every parameter and the baseline would be 3. The description adds value by grouping the inputs into a narrative (persona, stage, objective plus solution, pain, value prop, proof, ask) and by implying that whichever optional inputs are supplied shape the output and any omissions are surfaced back to the caller.

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 makes clear it produces outreach email sequences and specifies the concrete artifact ('each email with its subject, send day and body'). The opening sentence is framed abstractly ('Helps you decide what to send, and when') rather than as a direct verb+resource statement, but the rest of the paragraph removes any ambiguity about what is produced.

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

Usage Guidelines4/5

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

It gives an explicit routing rule: use this instead of sales_enablement_content when you need scheduled outreach emails with subjects and send days. It also names the covered objectives (prospecting, nurture, follow up, re engagement), which helps an agent match intent. It stops short of stating when not to use it beyond that single alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.