Argorant

Create an email campaign (draft)

argorant_create_campaign

Create a new campaign as a draft with its sending schedule. Nothing is sent until argorant_launch_campaign. Use it to start a new campaign; to reuse an existing campaign's emails and settings use argorant_duplicate_campaign. Next, add the emails with argorant_set_campaign_emails, the people with argorant_add_campaign_leads and the mailboxes with argorant_set_campaign_senders. New campaigns start with bounce protection and stop on reply switched on, leave out addresses that bounced for other Argorant users, and never get an unsubscribe line unless the user asks for one; argorant_update_campaign changes all of these. Returns the new campaign with its campaign_id. More in the docs at https://docs.argorant.com/docs/agents/tools#campaigns

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": {
      "name": "<name>"
    },
    "name": "argorant_create_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The campaign's name as the user sees it.
`timezone`	No	Time zone of the sending window, such as America/New_York (the default).	America/New_York
`plain_text`	No	Kept for older clients. Campaigns always send plain text.
`daily_limit`	No	Most emails the whole campaign sends a day (default 100).
`gap_minutes_max`	No	Longest gap in minutes between two emails from the same mailbox (default 120). Each gap is picked at random in between.
`gap_minutes_min`	No	Shortest gap in minutes between two emails from the same mailbox (default 60). 60 to 120 is the safe default for Microsoft mailboxes.
`planned_start_date`	No	First day sending may start after the launch, as YYYY-MM-DD. Left out, it starts on the launch day.
`skip_shared_bounces`	No	Also leave out addresses that bounced for other Argorant users (default true, recommended).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say it is a non-destructive write; the description adds genuinely new behavior: nothing is sent until launch, new campaigns default to bounce protection and stop-on-reply, shared bounces are excluded by default, no unsubscribe line appears unless requested, and argorant_update_campaign overrides all of these. It also notes the payload includes campaign_id, which the agent needs for the follow-up calls.

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?

Front-loaded with purpose, then alternative, then workflow, then defaults, then return value, then a docs pointer, so the ordering is sensible and no sentence is filler. The defaults sentence is long and carries four separate facts, which slightly hurts scannability.

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?

For an 8-parameter creation tool with an output schema, the description covers everything the agent needs decision-wise: draft semantics, sibling choice, required follow-up calls, default settings, and where return data lands. Return-value detail is correctly left to the output schema.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter carries its own description with defaults and ranges, so the schema already does the heavy lifting. The description only hints at the scheduling aspect via 'with its sending schedule' and repeats the shared-bounce default that skip_shared_bounces already documents, adding little meaning beyond structured data.

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?

States a specific verb and resource ('Create a new campaign as a draft with its sending schedule') and immediately scopes the result as non-sending. It explicitly names argorant_duplicate_campaign as the contrasting sibling, so an agent can route between the two without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('start a new campaign'), an explicit when-not/alternative ('to reuse an existing campaign's emails and settings use argorant_duplicate_campaign'), and the downstream sequence of argorant_set_campaign_emails, argorant_add_campaign_leads and argorant_set_campaign_senders. It also flags argorant_launch_campaign as the gate for actually sending.

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

All Argorant tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.