Skip to main content
Glama

Manage Email Outreach Queue

manage_email_outreach_queue
Destructive

Bulk operations (status, approve-all, cancel_all) act on the current agent's queue when run inside an agent, and across the whole account from account-level chat — except a bulk cancel_all or approve-all, which from account-level chat is rejected unless agent_id names the campaign, so it can't hit every campaign at once. Targeting one person by recipient_email reaches them in any agent. The next send time and per-mailbox usage stay account-wide (the send rate is per-mailbox).

For pausing/resuming the campaign, use update_agent to set the agent status to 'paused' or 'active' instead. Dict with action result and current queue status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoFor 'update' — new body text.
actionYesOne of: - 'status': Get full queue details (pending/sent/failed items). The `pending_items` / `pending_approval_items` lists cap at 50 each, each with a `pending_truncated` / `pending_approval_truncated` flag — when a list's flag is True, pass `offset` (offset += 50) to read the next page. Each item carries the `mailbox` it sends from; the account-level `mailboxes` list gives each mailbox's remaining daily headroom. The top-level `cancelled_by_kind` maps each cancel cause to its count (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy rows under `unknown`) — read it to answer "how much outreach was cancelled, and why?". - 'update': Edit a queued email's subject and/or body. Requires recipient_email. Pass subject and/or body to change — no cancel-and-re-queue needed. Send order is derived, not per-row scheduled; to pause or resume the campaign use update_agent (see the note above). A draft on a step running an A/B test carries `ab_version` ('A', 'B', or 'left_out' when its send won't count) on its status row and in this action's result; updating one takes ab_version too — the version the edited draft reads as — or ab_version alone to re-file it unedited. - 'approve': Send authorization belongs to the user, so this action needs a message that arrived after the drafts were queued and explicitly says to approve or send them. A message from before the drafts existed cannot authorize them — a request to review them, to approve them later, or to be able to approve from chat means: report that the queue is awaiting approval and end your turn; the user's next message decides. Once authorized: if recipient_email is given, approve only that item, otherwise approve ALL pending_approval items. An email whose subject or body still holds a [[slot]] for the user to fill in stays awaiting approval and comes back in `still_held` with the slot to fill: tell the user, or fill it with 'update' once they give you the wording. From account-level chat an approve-all is rejected unless agent_id names the campaign — it must not fire every campaign's drafts into sending at once. - 'cancel': Cancel a queued email. Pass recipient_email to cancel that one person. To cancel the ENTIRE pending queue — which drops drafts the user already approved — you must pass cancel_all=True; an unscoped cancel without it is rejected. From account-level chat a cancel_all is rejected unless agent_id names the campaign to cancel — it must not clear every campaign's queue at once.
offsetNoFor 'status' only — skip this many items in each queued list before returning the next 50. Use it to page through a queue larger than 50 (offset=50 for items 51-100, etc.).
subjectNoFor 'update' — new subject line.
agent_idNoFor 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one campaign's queue. Required from account-level chat (no active agent) and in any call with on_behalf_of, where an unscoped bulk cancel or approve is rejected; call list_agents to get the id (list_team_shared_agents for a teammate's campaigns).
ab_versionNoRequired for 'update' of a draft in an A/B test — the version the edited draft now reads as: 'A', 'B', or 'left_out' when it fits neither, so its send isn't counted in the test; its current version when the edit doesn't change that. Omit for a draft not in a test.
cancel_allNoFor 'cancel' only — confirm a queue-wide cancel when no recipient_email is given. Guards against silently tearing down the whole campaign.
on_behalf_ofNoA teammate's email (one with team actions turned on), or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
recipient_emailNoFor 'update', 'approve', and 'cancel' — target a specific recipient. Leave empty to apply to all items (not valid for 'update'; for 'cancel', requires cancel_all=True).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above). A draft on a step running an A/B test\n  carries `ab_version` ('A', 'B', or 'left_out' when its send won't count) on its\n  status row and in this action's result; updating one takes ab_version too — the\n  version the edited draft reads as — or ab_version alone to re-file it unedited.\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless agent_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless agent_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."New value: +"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above). A draft on a step running an A/B test\n  carries `ab_version` ('A', 'B', or 'left_out' when its send won't count) on its\n  status row and in this action's result; updating one takes ab_version too — the\n  version the edited draft reads as — or ab_version alone to re-file it unedited.\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. An email whose subject or body still holds a\n  [[slot]] for the user to fill in stays awaiting approval and comes back in\n  `still_held` with the slot to fill: tell the user, or fill it with\n  'update' once they give you the wording. From account-level chat an\n  approve-all is rejected unless agent_id names the campaign — it must not\n  fire every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless agent_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."
    • changedInput schema / properties / agent_id / description
      Previous value: -"For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active agent), where an\n    unscoped bulk cancel or approve is rejected; call list_agents to get the id."New value: +"For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active agent) and in any\n    call with on_behalf_of, where an unscoped bulk cancel or approve is rejected; call\n    list_agents to get the id (list_team_shared_agents for a teammate's campaigns)."
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"Act on a consented teammate's email queue instead of your own —\npass their email. Covers approve / cancel / update / status; a bulk\napprove-all / cancel_all must name one of the teammate's campaigns via\nagent_id. Gated on that teammate's act-on-behalf setting; a teammate who\nhasn't granted it is rejected. Omit for your own.\nOr pass an agency client's email, from list_agency_clients, to run the call in that client's account, where none of the teammate limits above apply."New value: +"A teammate's email (one with team actions turned on), or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Changed2 schema fields changed
    • removedInput schema / properties / as_teammate
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Act on a consented teammate's email queue instead of your own —\npass their email. Covers approve / cancel / update / status; a bulk\napprove-all / cancel_all must name one of the teammate's campaigns via\nagent_id. Gated on that teammate's act-on-behalf setting; a teammate who\nhasn't granted it is rejected. Omit for your own."
      -}
    • addedInput schema / properties / on_behalf_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Act on a consented teammate's email queue instead of your own —\npass their email. Covers approve / cancel / update / status; a bulk\napprove-all / cancel_all must name one of the teammate's campaigns via\nagent_id. Gated on that teammate's act-on-behalf setting; a teammate who\nhasn't granted it is rejected. Omit for your own.\nOr pass an agency client's email, from list_agency_clients, to run the call in that client's account, where none of the teammate limits above apply."
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / ab_version
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "Which version of a step's A/B test a queued draft counts under, or LEFT_OUT of the test.",
      +      "enum": [
      +        "A",
      +        "B",
      +        "left_out"
      +      ],
      +      "title": "DraftVersion",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Required for 'update' of a draft in an A/B test — the version the edited\ndraft now reads as: 'A', 'B', or 'left_out' when it fits neither, so its send isn't\ncounted in the test; its current version when the edit doesn't change that. Omit\nfor a draft not in a test."
      +}
    • changedInput schema / properties / action / description
      Previous value: -"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above).\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless agent_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless agent_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."New value: +"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above). A draft on a step running an A/B test\n  carries `ab_version` ('A', 'B', or 'left_out' when its send won't count) on its\n  status row and in this action's result; updating one takes ab_version too — the\n  version the edited draft reads as — or ab_version alone to re-file it unedited.\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless agent_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless agent_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."
  4. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above).\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless task_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless task_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."New value: +"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above).\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless agent_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless agent_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."
    • addedInput schema / properties / agent_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active agent), where an\n    unscoped bulk cancel or approve is rejected; call list_agents to get the id."
      +}
    • changedInput schema / properties / as_teammate / description
      Previous value: -"Act on a consented teammate's email queue instead of your own —\npass their email. Covers approve / cancel / update / status; a bulk\napprove-all / cancel_all must name one of the teammate's campaigns via\ntask_id. Gated on that teammate's act-on-behalf setting; a teammate who\nhasn't granted it is rejected. Omit for your own."New value: +"Act on a consented teammate's email queue instead of your own —\npass their email. Covers approve / cancel / update / status; a bulk\napprove-all / cancel_all must name one of the teammate's campaigns via\nagent_id. Gated on that teammate's act-on-behalf setting; a teammate who\nhasn't granted it is rejected. Omit for your own."
    • removedInput schema / properties / task_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active task), where an\n    unscoped bulk cancel or approve is rejected; call list_agents to get the id."
      -}
  5. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_task (see the note above).\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless task_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless task_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."New value: +"One of:\n- 'status': Get full queue details (pending/sent/failed items). The\n  `pending_items` / `pending_approval_items` lists cap at 50 each, each\n  with a `pending_truncated` / `pending_approval_truncated` flag — when a\n  list's flag is True, pass `offset` (offset += 50) to read the next page.\n  Each item carries the `mailbox` it sends from; the account-level\n  `mailboxes` list gives each mailbox's remaining daily headroom. The\n  top-level `cancelled_by_kind` maps each cancel cause to its count\n  (`recipient_replied`, `task_deleted`, `auto_shelved`, …; pre-taxonomy\n  rows under `unknown`) — read it to answer \"how much outreach was\n  cancelled, and why?\".\n- 'update': Edit a queued email's subject and/or body. Requires recipient_email.\n  Pass subject and/or body to change — no cancel-and-re-queue needed. Send order\n  is derived, not per-row scheduled; to pause or resume the campaign use\n  update_agent (see the note above).\n- 'approve': Send authorization belongs to the user, so this action\n  needs a message that arrived after the drafts were queued and\n  explicitly says to approve or send them. A message from before the\n  drafts existed cannot authorize them — a request to review them,\n  to approve them later, or to be able to approve from chat means:\n  report that the queue is awaiting approval and end your turn; the\n  user's next message decides. Once authorized: if recipient_email\n  is given, approve only that item, otherwise approve ALL\n  pending_approval items. From account-level chat an approve-all is\n  rejected unless task_id names the campaign — it must not fire\n  every campaign's drafts into sending at once.\n- 'cancel': Cancel a queued email. Pass recipient_email to cancel that one\n  person. To cancel the ENTIRE pending queue — which drops drafts the user\n  already approved — you must pass\n  cancel_all=True; an unscoped cancel without it is rejected. From\n  account-level chat a cancel_all is rejected unless task_id names the campaign\n  to cancel — it must not clear every campaign's queue at once."
    • changedInput schema / properties / task_id / description
      Previous value: -"For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active task), where an\n    unscoped bulk cancel or approve is rejected; call list_tasks to get the id."New value: +"For 'cancel' and 'approve' — scope a bulk cancel_all / approve-all to one\n    campaign's queue. Required from account-level chat (no active task), where an\n    unscoped bulk cancel or approve is rejected; call list_agents to get the id."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations mark this as destructive, and the description substantiates that with critical warnings: cancel_all drops already-approved drafts, approve-all can fire every campaign unless scoped, and account-level bulk operations are rejected without agent_id. It also explains the approval authorization requirement in useful detail beyond the annotations.

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?

The description is front-loaded and structured around the main purpose, bulk behavior, and the update_agent alternative. It is lengthy for a tool description, but most of the length is justified by the destructive multi-action semantics and approval edge cases.

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?

Given nine parameters, destructive bulk operations, approval authorization nuances, and no output schema, the description provides enough behavioral context for correct invocation. The action enum in the schema covers status return details, so the description does not need to restate them.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description still adds meaningful cross-parameter context about bulk scope, account-level rejection behavior, and the need for agent_id in certain bulk calls, though much of the per-parameter detail is already present in 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 names the exact resource (email outreach queue) and the concrete operations: check status, update/cancel items, and approve pending items. It also distinguishes the tool from update_agent for pausing/resuming campaigns, so an agent can select it confidently.

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?

It explicitly states when to use each action (status, update, approve, cancel), including how bulk operations behave inside an agent versus account-level chat. It also gives a direct alternative for campaign pausing/resuming and clear approval authorization rules.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources