@talqing/mcp 0.5.0 → 0.7.0

package/SKILL.md

@@ -1144,8 +1144,16 @@ overrides of anything else — one batch is one agent, one number, one clock.
 weekdays it may dial in, so a list uploaded at 23:00 can start at 11:00
 tomorrow, stop at 18:00 and resume at 10:00 on the next weekday untouched. A
 window may cross midnight; the days then name the evening it starts on.
-`next_dial_at` on the batch says when it will dial next, which is how you tell
-"waiting for Monday" apart from "stuck".
+`next_dial_at` on the batch says when it will dial next and `next_dial_reason`
+why (`start`, `window`, `daily_cap`), which is how you tell "waiting for Monday"
+apart from "stuck".
+
+**Pace.** `dial_gap_seconds` is the minimum wait between starting two calls (0,
+the default, dials as slots free). `dial_daily_cap` limits calls placed per
+local day, retries included: `{kind: "fixed", limit}` or a ramp, `{kind: "ramp",
+start, end, step, interval_days}`, which rises by `step` every `interval_days`
+days the batch actually dialled. For a new caller ID suggest a ramp rather than
+a flat limit. `dialed_today` is measured against `dial_daily_cap_today`.
 
 **Say these two things before creating one**, because a user who discovers
 either from an invoice will not forgive us:
@@ -1159,8 +1167,8 @@ either from an invoice will not forgive us:
 **Steering it.** `pause_call_batch` stops new calls and lets live ones finish;
 `resume_call_batch` carries on. `cancel_call_batch` is final and there is no
 delete — a batch is the record of money spent. `add_call_batch_recipients`
-appends to a running batch and silently skips numbers it already holds, so
-re-uploading an exported list never calls anyone twice.
+appends to a batch — a completed one starts dialling again — and skips numbers
+it already holds, so re-uploading an exported list never calls anyone twice.
 
 **Watching it.** `get_call_batch` has live counts and `failure_reason`; a batch
 that stops itself did so after ten consecutive setup failures (an unpublished
@@ -1180,8 +1188,8 @@ afterwards will not forgive us:
 - **Resend's terms prohibit unsolicited email, cold outreach, purchased lists
   and scraped contact data**, and require that every recipient has explicitly
   opted in. This runs on *their* Resend account under *their* agreement.
-- **Nothing is sent that they have not reviewed and selected.** Creating a batch
-  only drafts.
+- **Creating a batch only drafts.** Nothing is sent until someone creates a
+  send — and a send of every row mails drafts nobody reviewed.
 - **Every row runs the task's CURRENT PUBLISHED version**, re-read as drafting
   goes, so publishing mid-batch changes every row drafted after that moment. Which version
   wrote which rows is on the batch as `drafted_versions`, and
@@ -1242,7 +1250,10 @@ row. `create_email_send` takes a `scope` and returns a **send** you can steer:
 - `start_at` schedules it, `window` (on its own `timezone`) holds it to business
   hours, `send_gap_seconds` is the minimum wait between two emails of the
   **batch** (1 second to 1 hour) and `send_daily_cap` bounds how many the batch
-  may send per local day. Anything omitted comes from the batch.
+  may send per local day: `{kind: "fixed", limit}`, or a ramp, `{kind: "ramp",
+  start, end, step, interval_days}`, which rises by `step` every `interval_days`
+  days the batch actually sent (a weekend or a pause earns nothing). Anything
+  omitted comes from the batch.
 - A draft a live send covers reads `queued`, and is still a draft: it can be
   edited, skipped or redrafted until the send takes it.
 - `pause_email_send` stops on the next email; `resume_email_send` carries on.
@@ -1254,9 +1265,10 @@ row. `create_email_send` takes a `scope` and returns a **send** you can steer:
   within five minutes, so raising a spent cap or removing a window needs no
   cancel.
 
-**The safeguard here is a RATE, not a row count.** `send_daily_cap` (200 by
-default, per batch, `null` for uncapped) is what stands between a 5 000-row list
-and a sending domain nobody trusts again. Before creating a send, say how many
+**The safeguard here is a RATE, not a row count.** `send_daily_cap` (a fixed
+200 by default, per batch, `null` for uncapped) is what stands between a
+5 000-row list and a sending domain nobody trusts again. For a new sending
+domain, suggest a ramp (say 10 rising to 50) rather than a flat cap. Before creating a send, say how many
 emails it is and roughly how long it will take at the pace it has — and if the
 user asks to raise or remove the cap, say what it is for rather than just doing
 it.
@@ -1288,6 +1300,10 @@ count before running `all`. A person's edited cells survive unless
 the new draft. Read `draft_failures` before redrafting `failed`: a task that
 declined a row on purpose will most likely decline it again.
 
+`add_email_batch_recipients` appends rows, skipping duplicates, and a drafted
+batch drafts again. If the latest send is a finished send of every row it
+reopens and mails them unreviewed (`standing_send_id`), so say so first.
+
 **One address is mailed at most once per batch**, enforced when the row is
 claimed for sending: the second row settles `skipped` with
 `duplicate_recipient`. There is no cross-batch dedup and no suppression list of
@@ -1297,7 +1313,7 @@ ours — Resend keeps one and auto-suppresses hard bounces and complaints.
 
 `get_email_batch` carries live counts, `skips` (why rows were skipped),
 `draft_failures` (why drafts failed, most common first), `failure_reason`,
-`sent_today` (against `send_daily_cap`), `drafted_versions`,
+`sent_today` (against `send_daily_cap_today`), `drafted_versions`,
 `stale_redraftable` / `stale_sent` and the drafting cost so far. Measure
 progress against what can be reached: `unfillable` rows are never drafted, and
 skipped, failed or cancelled rows are never sent.
@@ -1321,7 +1337,9 @@ gives a sender's approved templates — header, body, footer, buttons and variab
 names; one with `unsupported_reason` cannot be used.
 `create_whatsapp_batch` maps `to_column` and every variable onto CSV columns. A
 row with a bad or repeated phone, or a blank mapped cell, is kept and skipped
-with the reason, so read the returned `counts`.
+with the reason, so read the returned `counts`. `send_daily_cap` takes the same
+object an email batch's does (a fixed 250 by default); for a new sender suggest
+a ramp.
 
 **Say these before creating one:**
 
@@ -1331,6 +1349,8 @@ with the reason, so read the returned `counts`.
   templates any one person receives.
 - **You cannot send it.** `send_whatsapp_batch` and `resume_whatsapp_batch` are
   a person's to press, on the batch page. Create the batch, point them at it.
+- **`add_whatsapp_batch_recipients` on a sending or completed batch messages
+  the new rows at once**, with nobody pressing anything. Get an explicit yes.
 
 Replies are answered by the agent on the sender's
 `whatsapp.message.inbound` trigger, which sees the row's columns as

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@talqing/mcp",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "MCP server for building Talqing AI voice, video and text agents from Claude Code, Codex, or any MCP client.",
   "license": "MIT",
   "homepage": "https://talqing.com",

package/tools.json

@@ -1081,7 +1081,7 @@
       "role": "read"
     },
     {
-      "description": "Change a batch's policy while it runs. The next pass picks it up.",
+      "description": "Change a batch's policy while it runs or after it completes. The next pass reads it.",
       "method": "PATCH",
       "name": "patch_call_batch",
       "parameters": {
@@ -1109,7 +1109,7 @@
       "role": "read"
     },
     {
-      "description": "Append people to a batch, including one that is already running.",
+      "description": "Append people to a batch, including one that has finished \u2014 it resumes.",
       "method": "POST",
       "name": "add_call_batch_recipients",
       "parameters": {
@@ -1123,7 +1123,7 @@
       "role": "write"
     },
     {
-      "description": "Stop placing new calls. Calls already in progress run to their end.",
+      "description": "Stop placing new calls; calls in progress run to their end.",
       "method": "POST",
       "name": "pause_call_batch",
       "parameters": {
@@ -1290,6 +1290,20 @@
       "read_only": true,
       "role": "read"
     },
+    {
+      "description": "Append rows to a batch; a drafted batch resumes. Duplicates are skipped and reported.",
+      "method": "POST",
+      "name": "add_email_batch_recipients",
+      "parameters": {
+        "additionalProperties": true,
+        "description": "Arguments not inlined: call describe_function('add_email_batch_recipients').",
+        "properties": {},
+        "type": "object"
+      },
+      "path": "/v1/email/batches/{batch_id}/recipients",
+      "read_only": false,
+      "role": "write"
+    },
     {
       "description": "Edit cells on one row before it is sent.",
       "method": "PATCH",
@@ -1556,6 +1570,20 @@
       "read_only": true,
       "role": "read"
     },
+    {
+      "description": "Append rows; repeated numbers are skipped. **Messages them if sending or completed.**",
+      "method": "POST",
+      "name": "add_whatsapp_batch_recipients",
+      "parameters": {
+        "additionalProperties": true,
+        "description": "Arguments not inlined: call describe_function('add_whatsapp_batch_recipients').",
+        "properties": {},
+        "type": "object"
+      },
+      "path": "/v1/whatsapp/batches/{batch_id}/recipients",
+      "read_only": false,
+      "role": "write"
+    },
     {
       "description": "Edit cells on a row not yet sent, its phone included. An empty value clears the edit.",
       "method": "PATCH",