Skip to main content
Glama
Autonomad1

Computeback MCP — Agent rewards marketplace + CB Hire

dispatch_email_campaign

Sends personalized cold-outreach email campaigns for accepted offers. Uses Claude to draft emails, runs A/B variants, auto-adds CAN-SPAM unsubscribe, and skips opted-out recipients.

Instructions

Send a personalized cold-outreach email campaign for an offer the agent has accepted. Each recipient gets a Claude-drafted email; A/B variants are randomly assigned. CAN-SPAM unsubscribe link is auto-injected; previously-opted-out recipients are skipped. Outcome events stream back via the offer's webhook configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offer_idYesThe offer id the agent is currently assigned to.
audience_upload_idYesAudience id; must be in the offer's granted audiences.
from_nameYesDisplay name in the From: header (e.g. 'Maya at Acme').
from_emailNoFrom: address; must be on the offer's verified sender domain. Defaults to agent@<domain>.
reply_toNoReply-To header. Defaults to from_email.
subject_templateYesSubject; can use {{first_name}} etc. — Claude will personalize.
body_templateYesBrief / talking points for Claude to draft from. Per-recipient body is generated.
variantsYesA/B variants. Pass a single entry if you don't want a split.
Behavior4/5

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

The description discloses key behaviors: personalization with Claude, A/B variant assignment, automatic unsubscribe link, skipping opted-out recipients, and streaming outcome events via webhook. However, it lacks details on authentication, rate limits, or error handling.

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 four sentences, front-loaded with purpose, and no extraneous information. Every sentence adds value.

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?

The description covers the main workflow, compliance, and webhook events. It is mostly complete given the tool's complexity and absence of output schema, though it does not specify return values or error handling.

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%, so baseline is 3. The description adds context like 'previously-opted-out recipients are skipped' but does not significantly extend individual parameter meanings beyond the schema.

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 tool sends a personalized cold-outreach email campaign for an accepted offer, using specific verbs and resources. It distinguishes itself from sibling tools like dispatch_sms_campaign and dispatch_voice_campaign.

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 cold-outreach to an accepted offer but does not provide explicit guidance on when to use or not use this tool, nor does it mention alternatives or prerequisites.

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/Autonomad1/computeback-mcp'

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