Skip to main content
Glama

migration_retryFailedJobs

Resets retries on failed migration jobs across one or more batches, returning total retried counts and a per-batch breakdown so stalled migrations can resume.

Instructions

Reset retries on all failed migration jobs in one or more batches. Returns total retried count and per-batch breakdown.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "batchIds": "<batchIds>"
    },
    "name": "migration_retryFailedJobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
retriesNoNumber of retries to set (default: 1)
batchIdsYesBatch IDs whose failed jobs should have retries reset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / properties / batchIds
      Added value: +{
      +  "description": "Batch IDs whose failed jobs should have retries reset",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / retries
      Added value: +{
      +  "description": "Number of retries to set (default: 1)",
      +  "type": "number"
      +}
    • addedInput schema / required
      Added value: +[
      +  "batchIds"
      +]
  2. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return shape (total retried count plus per-batch breakdown), which is valuable with no output schema, but it leaves open whether jobs are actually re-executed or only their retry counters are set, and says nothing about required permissions or side effects on already-succeeded jobs.

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?

Two short sentences with zero waste: the action and scope come first, the return value second. Nothing is repeated and nothing is padding.

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?

With no annotations and no output schema, the description is reasonably complete on inputs and returns for a two-parameter mutation. It still omits the state preconditions and the exact semantics of 'reset' versus 'retry', which matter for a job-mutating 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 the schema already documents both batchIds and retries including the default of 1. The description adds only the plural framing ('one or more batches'), which the array type already conveys, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reset retries on failed migration jobs, scoped to one or more batches. An agent can distinguish it from migration_getBatchFailures or migration_resumeBatch, though the description never names those alternatives explicitly.

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?

Usage is implied by the phrase 'failed migration jobs', suggesting this is the tool for retrying failures. However, there is no explicit when-to-use guidance and no mention of prerequisites such as whether the batch must be suspended, or when to prefer this over resumeBatch/executeBatch for the same failures.

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