Give your agent a growth job

The CSV stays with your assistant or MCP client. There is no separate server-side CSV upload endpoint. Quote CSV fields that contain commas, quotation marks, or line breaks. Leave reply_url empty for a DM, then omit that field from its JSON row.

row_id,action,handle,reply_url,message
reply-001,reply,example_handle,https://x.com/example_handle/status/1234567890123456789,"Your approved public reply goes here."
dm-001,dm,example_handle,,"Your approved direct message goes here."

Arguments for smore_submit_x_outreach

Get the real connection_id from smore_list_x_connections. Omit schedule for immediate eligibility and omit pacing to use the default 45 to 240 second range.

{
  "connection_id": "11111111-1111-4111-8111-111111111111",
  "idempotency_key": "approved-outreach-2026-10-08-v1",
  "schedule": {
    "local_start_at": "2026-10-08T07:00:00",
    "time_zone": "America/Los_Angeles"
  },
  "pacing": {
    "min_delay_seconds": 45,
    "max_delay_seconds": 240
  },
  "rows": [
    {
      "row_id": "reply-001",
      "action": "reply",
      "handle": "example_handle",
      "reply_url": "https://x.com/example_handle/status/1234567890123456789",
      "message": "Your approved public reply goes here."
    },
    {
      "row_id": "dm-001",
      "action": "dm",
      "handle": "example_handle",
      "message": "Your approved direct message goes here."
    }
  ]
}

Invalid rows, unknown fields, duplicate keys or row IDs, and malformed destinations reject the whole submission before anything is queued. DM handles resolve to their current numeric X identity at dispatch, which is saved before sending.

Submission returns batch_id, status, sender, resolved UTC start, pacing, expiry, progress counts, and next_send_at when applicable. Use smore_get_x_outreach with {"batch_id":"…","limit":50} to read row results. The maximum page size is 100; pass the returned next_cursor back as cursor unchanged.

Batch states are scheduled, queued, running, paused, completed, cancelled, or failed. Inspect the per-row outcomes and progress counts; completed does not mean every message was sent successfully. Rows retain your original ID, destination and message, plus attempts, error code, and dispatch/finish times when available. Receipts prove provider acceptance, not that someone read or answered.

Submitting the same key with identical input returns the original batch. Changing the sender, text, destination, schedule, or pacing under that key produces idempotency_conflict. A timeout or lost provider response becomes send_unknown; do not create a new batch to repeat an unresolved write. A late confirmed receipt can update the existing outcome.

Call smore_cancel_x_outreach with {"batch_id":"…"} to stop remaining queued messages. Cancellation cannot retract a sent message or guarantee stopping one already dispatched. Grant revocation or expiry, membership removal, or account/workspace closure stops remaining unauthorized work while preserving known outcomes.

MCP errors use isError: true with a safe code and message. Relevant codes include invalid_request, idempotency_conflict, paid_required, connection_required, insufficient_scope, invalid_token, not_found, and outreach_disabled.

The accepted batch pauses and returns a reconnect action through smore_get_x_outreach. This is a batch status, rather than a failed submission. An example of the relevant return fields:

{
  "status": "paused",
  "code": "account_disconnected",
  "next_send_at": null,
  "next_action": {
    "type": "reconnect_x",
    "url": "https://app.makesmores.com/app/settings?outreach_batch_id=22222222-2222-4222-8222-222222222222&workspace_id=33333333-3333-4333-8333-333333333333",
    "requires_role": "owner_or_admin"
  },
  "resume_policy": "automatic_after_same_account_reconnect"
}

Your assistant should say: "Outreach is paused because the sending X account disconnected. Open the reconnect link, select the batch's workspace, and connect the same account. Pending rows will resume automatically."

An owner or administrator reconnects in the secure Settings form, including any provider challenge. S'more verifies the original numeric X identity; matching the handle alone is insufficient. A different account cannot take over the approved batch. After verification, pending rows resume within the batch's expiry. Sent and uncertain rows are not repeated.

A target_ref comes from find or waves and stays valid for 90 minutes after the post was read. With a target_post_url, S'more reads the post's author and link when it sends. Text is at most 280 X-weighted characters and is never trimmed. Receipts are X post links for all three modes.

Errors use isError: true with a safe code and message. Relevant codes include paid_required, watch_limit_reached, keyword_invalid, target_ref_expired, target_blocked, target_limit_reached, account_day_limit_reached, account_paused, media_too_large, approval_expired, approval_mismatch, approval_used, text_too_long, connection_required, idempotency_conflict, and rate_limited.

For clients that accept explicit OAuth scopes, request linkedin:outreach:read,linkedin:outreach:send,linkedin:outreach:cancel. S'more CLI v0.15.134 supports smore auth login --linkedin-outreach. This flag also requests the existing agent, run, lead, and scoring scopes; review every permission in the browser before approving it.

The CSV stays with your assistant or client, which parses it into MCP arguments. Quote fields containing commas or line breaks. Omit empty destination fields from each JSON row.

row_id,action,profile_url,reply_url,parent_comment_urn,message
dm-001,dm,https://www.linkedin.com/in/first-degree-recipient/,,,"Your approved DM."
comment-001,reply,,https://www.linkedin.com/feed/update/urn:li:activity:1234567890123456789/,,"Your approved comment."
nested-001,reply,,https://www.linkedin.com/feed/update/urn:li:activity:1234567890123456789/,"urn:li:comment:(urn:li:activity:1234567890123456789,1234567890123456790)","Your approved nested reply."
invite-001,connect,https://www.linkedin.com/in/example-recipient/,,,"Your approved invitation note."

Arguments for one invitation

Get the actual sender's connection_id from the list tool. This one-row request uses smore_submit_linkedin_outreach and does not schedule a later DM.

{
  "connection_id": "11111111-1111-4111-8111-111111111111",
  "idempotency_key": "approved-linkedin-invitation-2026-10-08-v1",
  "schedule": {
    "local_start_at": "2026-10-08T07:00:00",
    "time_zone": "America/Los_Angeles"
  },
  "pacing": {"min_delay_seconds": 45, "max_delay_seconds": 240},
  "rows": [{
    "row_id": "invite-001",
    "action": "connect",
    "profile_url": "https://www.linkedin.com/in/example-recipient/",
    "message": "Your approved invitation note."
  }]
}

S'more preserves spaces, line breaks, and the full note. Invalid fields, duplicate keys or row IDs, malformed text, and unsupported destinations reject submission before it queues anything. Use canonical links without URL credentials, explicit ports, or fragments.

Start time and pacing

Omit schedule for immediate eligibility. A one-time schedule uses local YYYY-MM-DDTHH:mm:ss without an offset and an explicit IANA zone. Default spacing is a persisted random 45 to 240 seconds, shared across batches using the same LinkedIn member in that workspace. It survives restarts; provider waits can extend it.

The shared scheduling and result rules apply: a default 30-day scheduling horizon, rejection of ambiguous or nonexistent daylight-saving times, expiry seven days after the resolved start including pauses, and optional pacing bounds of 15 to 300 seconds with minimum no greater than maximum. The start time is the earliest eligible time.

Submission returns the batch ID, sender, resolved start, expiry, pacing, progress, and next_send_at. Get returns row IDs, exact messages, destinations, attempts, safe error codes, timestamps, and confirmed external_id values when available. A verified public comment URL may appear as receipt_url; DMs and invitations have no invented public links.

The shared row statuses, replay, and cancellation rules apply. A sent receipt records provider acceptance, not reading, response, or invitation acceptance. A completed batch can contain failures. A send_unknown write may have succeeded and is never automatically repeated; later writes from that account pause. Do not submit a new batch to repeat an unresolved write.

Cancellation stops unstarted rows and leaves earlier or already dispatched work intact. It does not withdraw invitations or remove comments or DMs. Identical input under the same key returns the original batch; changing the sender, rows, text, destinations, schedule, or pacing produces idempotency_conflict.

If the sender disconnects, the batch pauses. Relevant return fields:

{
  "status": "paused",
  "code": "account_disconnected",
  "next_send_at": null,
  "next_action": {
    "type": "reconnect_linkedin",
    "url": "https://app.makesmores.com/app/settings?platform=linkedin&outreach_batch_id=22222222-2222-4222-8222-222222222222&workspace_id=33333333-3333-4333-8333-333333333333",
    "requires_role": "owner_or_admin"
  },
  "resume_policy": "automatic_after_same_account_reconnect"
}

Your assistant should prompt: "LinkedIn outreach is paused because the sending account disconnected. Open the reconnect link, select this batch's workspace, and reconnect the same LinkedIn account. Pending rows will resume within the batch's expiry."

S'more verifies the original member identity; a matching nickname, email, or profile URL is insufficient. A different account cannot take over the batch. Sent and uncertain rows remain unchanged.

What this feature covers

This feature sends finished outreach. It excludes discovery, drafting, inbox reads, incoming-response tracking, invitation-acceptance polling, recurring schedules, and follow-up sequences. InMail, Open Profile messages, message requests, page senders, group DMs, and attachments are also outside this flow.

After rollout, clients with explicit OAuth scope support can request the scopes in this table. The CLI provides separate opt-ins; combine them when you need both sending and post drafts:

smore auth login --reddit-outreach --reddit-posts
smore mcp-proxy

Review all requested permissions in the browser. CLI login also requests the existing agent, run, lead, and scoring scopes, and keeps credentials in your OS keychain. S'more CLI v0.15.134 supports both flags; Reddit sending and generation remain pending rollout.

Choose the returned connection_id explicitly. Connection metadata includes account_key, reddit_user_id, username, status, and can_send. The server verifies the account again before dispatch. Managed discovery accounts cannot send. Optional thread context checks subreddit, ancestry, and locked, archived, or removed targets. If a required source is unavailable, the read returns an error.

The CSV stays with your assistant, which converts it to JSON rows. There is no separate CSV upload endpoint. Quote values containing commas, quotation marks, or line breaks. Empty cells for another action must be omitted from that JSON row.

row_id,action,subreddit,post_fullname,parent_comment_fullname,kind,title,body,link_url,recipient_username,message
comment-001,reply,example,t3_abc123,,,,,,,"Your approved comment."
nested-001,reply,example,t3_abc123,t1_def456,,,,,,"Your approved nested reply."
self-001,post,example,,,self,"Your approved title","Your approved body.",,,
link-001,post,example,,,link,"Your approved link title",,https://example.com/guide,,
dm-001,dm,,,,,,,,example_user,"Your approved chat message."

Arguments for smore_submit_reddit_outreach

{
  "connection_id": "11111111-1111-4111-8111-111111111111",
  "idempotency_key": "approved-reddit-campaign-v1",
  "rows": [
    {"row_id":"comment-001","action":"reply","subreddit":"example","post_fullname":"t3_abc123","message":"Your approved comment."},
    {"row_id":"nested-001","action":"reply","subreddit":"example","post_fullname":"t3_abc123","parent_comment_fullname":"t1_def456","message":"Your approved nested reply."},
    {"row_id":"self-001","action":"post","kind":"self","subreddit":"example","title":"Your approved title","body":"Your approved body."},
    {"row_id":"link-001","action":"post","kind":"link","subreddit":"example","title":"Your approved link title","link_url":"https://example.com/guide"},
    {"row_id":"dm-001","action":"dm","recipient_username":"example_user","message":"Your approved chat message."}
  ]
}

Validation limits

Every row needs a unique, nonblank row_id. Row IDs and the batch key allow up to 128 bytes. Batches accept 1 to 500 rows within a 1 MiB request, subject to server policy. Unknown fields, duplicate JSON keys or row IDs, and fields from another action reject the submission before enqueue.

Subreddit names use 2 to 21 letters, digits, or underscores without r/. Recipient usernames use 3 to 20 letters, digits, underscores, or hyphens without u/. Post IDs are t3_ plus 1 to 32 lowercase letters or digits; comment IDs use t1_ with the same suffix rule. Comments allow 10,000 Unicode code points, titles 300, text bodies 40,000, and DMs 4,000. Content must be nonblank; titles cannot contain line breaks.

Batch link URLs must be HTTP(S), at most 2,048 bytes, with no embedded credentials, whitespace, or control characters. Flair IDs allow up to 128 bytes without whitespace or control characters. Post flags default to nsfw: false, spoiler: false, and send_replies: true. An optional source_draft_id is the UUID of a saved draft in this workspace; it records lineage while your submitted content remains the approved content.

Optional conversation_id is a Reddit room ID such as !approved_room:reddit.com, with 1 to 255 letters, digits, periods, underscores, equals signs, or hyphens between ! and :reddit.com. Use a real returned room ID. The server resolves the approved username to its native Reddit identity before a write.

Omit schedule for immediate eligibility and pacing for defaults. The shared outreach reference gives the exact local-time and pacing objects, the default 30-day scheduling horizon, seven-day expiry, and 15 to 300 second pacing bounds. Reuse a key only for identical explicit input; changing any approved field returns idempotency_conflict.

smore_generate_reddit_posts produces 1 to 5 drafts. Supply either an existing workspace Reddit agent_id, or both an inline brief and voice. This example asks for one text post:

{
  "connection_id": "11111111-1111-4111-8111-111111111111",
  "idempotency_key": "reddit-post-review-v1",
  "count": 1,
  "subreddit": "example",
  "kind": "self",
  "brief": {
    "who": "Independent software founders",
    "signals": "Discuss how founders find their first customers",
    "never": "Invent results or promote an unrelated product",
    "goal": "Start a useful discussion about what worked"
  },
  "voice": "Plain language, short paragraphs, and a natural question"
}

For a link draft, use kind: link and supply the exact HTTPS link_url. Generation requires HTTPS even though an approved batch accepts HTTP(S). Optional flair_id must be available in the account's posting context. Optional source_link_ids accepts up to 32 unique workspace proof-link UUIDs that are enabled for drafting. Each brief field and the voice allow up to 20,000 Unicode code points.

The response includes request_id, status, model and prompt provenance, review_only: true, and saved posts with draft IDs. Questions and Markdown are supported. Retrieve a lost response with smore_get_reddit_posts: supply only the returned request_id, or use {"idempotency_key":"reddit-post-review-v1"}. Identical input keeps the original request and context; changed input under the same key conflicts. An interrupted generation call can repeat model work.

Review and edit each returned post, then copy its exact approved content into a post row for smore_submit_reddit_outreach. Including its source_draft_id does not substitute the generated text or approve sending.

Read results with smore_get_reddit_outreach and the returned batch_id, for example {"batch_id":"22222222-2222-4222-8222-222222222222","limit":50}. The default page has 50 rows; the maximum is 100. Pass a returned next_cursor unchanged as cursor. The shared batch and row states apply here: completed can include failed or uncertain rows. Results retain the exact approved content, attempt counts, safe error codes, timestamps, and receipts.

Confirmed comments have a t1_ receipt, posts a t3_ receipt, and chat messages an associated event ID. Receipts establish provider acceptance; they do not establish public visibility, reading, or a response.

A DM can pass through stage: dm_create and stage: dm_send. A confirmed room creation retains create_external_id and conversation_id; the row stays queued for its message. Check message_dispatched and the message receipt before reporting it as sent. Cancellation between the two steps preserves the room and stops the message.

If either write is uncertain, send_unknown and unknown_operation identify the unresolved step. S'more does not automatically repeat it, and later writes from that Reddit identity in the workspace wait. Do not create a replacement batch to repeat an unresolved operation. A matching late receipt can settle the original result.

Cancel remaining work with smore_cancel_reddit_outreach and {"batch_id":"22222222-2222-4222-8222-222222222222"}, replacing that placeholder with the returned ID. Already dispatched writes can finish, and cancellation does not retract published content. Grant expiry or revocation, membership removal, or account/workspace closure removes authority for remaining work.

If the sender needs renewal, the batch pauses and returns next_action.type: reconnect_reddit, a Settings link, and resume_policy: automatic_after_same_account_reconnect. An owner or administrator opens that link, selects the batch's workspace, and reconnects the same verified t2_ Reddit identity. The username alone is insufficient. Pending rows resume within expiry; sent and uncertain writes are not repeated.