Skip to main content
Glama

Rerun application workflow

rerun_application_workflow
Destructive

Rerun one of an Application's CI/CD workflow runs (rebuild). Use list_application_workflow_runs to find the run id.

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": {
      "application_id": "<application_id>",
      "run_id": "<run_id>"
    },
    "name": "rerun_application_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe workflow run id to rerun.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is conveyed structurally. The description adds '(rebuild)', hinting that a new run replaces or supersedes prior results, but it never states what is invalidated, whether history is preserved, or that repeated calls spawn additional runs. Useful but thin 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences: the action first, then the prerequisite lookup. No filler, no restating the title.

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

Completeness4/5

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

For a two-parameter, no-output-schema tool with annotations carrying the safety hints, the definition covers enough to invoke it correctly. The one gap is the absence of any post-rerun expectation (e.g., that a new run is created and can be tracked with watch_workflow_run), which would help an agent plan the next step.

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 coverage is 100% with two required parameters, so application_id and run_id are already fully documented. The description only adds sourcing guidance for run_id (fetch it from list_application_workflow_runs); it adds nothing about the run_id being integer-typed or application scoping. Baseline 3 is appropriate.

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 gives a specific verb plus resource ('Rerun ... an Application's CI/CD workflow runs') and clarifies with '(rebuild)', which distinguishes it from nearby siblings such as retry_application, redeploy_stack, or watch_workflow_run. An agent can identify the operation without opening the schema.

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?

It explicitly routes the agent to list_application_workflow_runs to obtain the run_id, which is the key prerequisite. It does not state when *not* to use it (e.g., versus retry_application for a failed deployment), so the exclusions are missing, but the positive guidance is clear.

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.