xmagnet

create_campaign

Create a DRAFT email campaign via a programmatic wizard. Call this tool and it will guide through the steps — no manual orchestration needed. WIZARD STEPS (handled automatically by the tool):

Call with contacts + total_contacts → tool returns engine picker (NextGen vs MyConvo)
Add campaign_type from user's click → tool returns campaign category chips (promotional, newsletter, event…)
Add campaign_category from user's click → tool returns engine-specific template gallery MyConvo: shows plain_email_templates (personal plain-text). NextGen: shows campaign_templates (HTML).
Add template_id from user's pick → tool creates the draft campaign. RULES: Reuse contacts from prior search — never re-search. Pass total_contacts from search result's total_in_crm so the user always sees the full count. Saves as DRAFT only — no emails sent.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	Email body (only needed for AI-generate path, not template path).
`name`	Yes	Campaign name
`tone`	No	Email tone — collected from user alongside campaign_description.
`subject`	No	Subject line (only needed for AI-generate path, not template path).
`contacts`	No	Contact objects from prior search to add as recipients.
`template_id`	No	Template ID selected by user from wizard step 3 gallery.
`from_account`	No	Sender email address (MyConvo only).
`campaign_type`	No	Engine chosen by user. Omit on first call — tool will prompt.
`total_contacts`	No	Total contact count from search result's total_in_crm. Always pass this so user sees full count.
`campaign_category`	No	Campaign category chosen by user. Omit until user picks from wizard step 2.
`campaign_description`	No	What the campaign is about — collected from user when no MyConvo templates found. Used to auto-generate plain-text content.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only indicate not read-only and not destructive. The description adds substantial behavioral detail: it is a multi-step wizard with intermediate returns (engine picker, category chips, template gallery), saves as DRAFT only, and sends no emails. This goes well beyond the annotation basics.

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 front-loaded with the purpose and then structured into clearly labeled 'WIZARD STEPS' and 'RULES.' Every sentence earns its place, providing necessary context without filler.

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?

Even without an output schema, the description covers the tool's full behavior: intermediate picks and their order, the final draft creation, and rules for contact reuse. Given the 11-parameter, multi-step complexity, this is a complete and self-sufficient description.

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?

Although schema coverage is 100%, the description adds critical semantics: which parameters to pass at each wizard step (e.g., omit campaign_type until prompted), body/subject only for the AI-generate path, and total_contacts sourced from total_in_crm. This meaningfully elevates the parameter understanding beyond schema descriptions.

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 'Create a DRAFT email campaign via a programmatic wizard,' using a specific verb and resource. It distinguishes itself from siblings like create_sequence_draft by focusing on campaigns and the draft state.

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?

The description provides explicit wizard steps and rules, such as 'Reuse contacts from prior search — never re-search' and 'Pass total_contacts from search result's total_in_crm.' While it doesn't name alternative tools for exclusion, it offers clear contextual guidance for when and how to invoke this tool.

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

All xmagnet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Several tools occupy nearly identical roles (create_contact/add_contacts/save_contacts_to_crm/upload_contacts; add_companies/create_company; search_contacts/search_crm_contacts/find_contacts_at_companies), and the names don't clearly reveal whether they operate on saved or prospected data. Although the descriptions clarify some boundaries, an agent would frequently need to read many descriptions carefully to avoid mis-selection.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern such as list_campaigns, create_deal, and update_contact. Minor deviations like company_intelligence, get_icp, load_more_contacts, and the inconsistent use of add_/create_/upload_/save_ for similar creation actions keep it from being fully consistent.

Tool Count1/5

51 tools is far beyond the well-scoped range and exceeds the 50+ extreme threshold. Even for a broad CRM/prospecting/marketing platform, exposing this many tools at once makes agent selection costly and unwieldy.

Completeness2/5

Contact and company creation/read/update are covered, but delete is absent across the board, and campaigns can be drafted, listed, and measured but not edited, activated, paused, or deleted. Deals, forms, and landing pages also lack update/delete lifecycle actions, creating meaningful dead ends for common CRM workflows.

Resources

Need Help?