Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

retryBulkCall

Destructive

Re-queue contacts from a finished bulk call campaign that did not connect, without creating a new campaign. Retry all failed contacts or only specific failure reasons while keeping original variables.

Instructions

Re-queue contacts that did not connect, without creating a new campaign.

Use it after a campaign finishes with more no-answers than you expected, or when the reason was on your side (a bad window, a number that was having a bad day). Retried contacts keep their original variables.

(Tags: Bulk calls)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyNoThe JSON request body.
bulk_call_idYesId of the bulk call campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.14.0
    • changedInput schema / properties / requestBody / properties / failure_reasons / description
      Previous value: -"Re-queue only contacts that failed for these reasons, for\nexample `no-answer` and `busy`.\n"New value: +"Statuses to re-queue. Read only when `retry_strategy` is\n`specific`; for example `no-answer` and `busy`. Ignored when\n`retry_strategy` is `all`.\n"
    • removedInput schema / properties / requestBody / properties / max_retries
      Removed value: -{
-  "description": "Skip contacts already retried this many times.",
-  "type": "number"
-}
    • changedInput schema / properties / requestBody / properties / retry_strategy / description
      Previous value: -"Which contacts to re-queue. `all` takes everything that did\nnot connect.\n"New value: +"Which contacts to re-queue. `all` takes everything that did\nnot connect. `specific` re-queues only the statuses listed\nin `failure_reasons`.\n"
  2. Addedv0.11.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false. The description adds genuine context that retried contacts keep their original variables and no new campaign is created, which softens the destructive picture. It does not disclose side effects such as duplicate calls, rate limits, or whether previously-connected contacts could be re-dialed, which matters for a destructive mutation.

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?

Three short sentences, with the outcome first and usage contexts after. Efficient, though the parenthetical aside on bad numbers/windows is slightly informal and the tag at the end is low value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive mutation with no output schema: the description says original variables are preserved and no new campaign is created, which is useful, but leaves out what the response contains, what happens with already-connected contacts, and any preconditions like campaign status. Adequate but incomplete for a destructive bulk operation.

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 description coverage is 100%, so retry_strategy and failure_reasons are fully documented in the schema. The description adds no parameter-level detail, but baseline 3 is appropriate since schema carries the burden.

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?

A specific verb (re-queue) and resource (contacts that did not connect) are stated, plus the key constraint that no new campaign is created. Together with the sibling set containing cancelBulkCall, getBulkCall, and startBulkCall, this clearly distinguishes the retry operation without schema inspection.

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

Usage Guidelines4/5

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

Gives clear use contexts: after a campaign finishes with more no-answers than expected, or when the failure was on your side (bad window, number issue). No explicit exclusions or named alternatives are given, keeping it at a 4 rather than a 5.

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

Deploy Server

Other Tools