Skip to main content
Glama

update_task_status

Update task execution status in Netflix Conductor workflows to track progress, mark completion, or report failures during workflow troubleshooting.

Instructions

Update the status of a task execution. This is typically used by workers to update task status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe unique task execution ID
workflowInstanceIdYesThe workflow instance ID
statusYesNew task status
outputNoTask output data
logsNoTask execution logs

Implementation Reference

  • The core handler function that implements the update_task_status tool. It constructs a task update object and sends a POST request to the Conductor API's /tasks endpoint to update the task status, output, and logs.
    case "update_task_status": {
      const { taskId, workflowInstanceId, status, output = {}, logs = [] } = args as any;
      
      const taskUpdate = {
        workflowInstanceId,
        taskId,
        status,
        outputData: output,
        logs,
      };
      
      await conductorClient.post("/tasks", taskUpdate);
      
      return {
        content: [
          {
            type: "text",
            text: `Task ${taskId} status updated to ${status} successfully.`,
          },
        ],
      };
    }
  • The tool schema definition providing the name, description, and input validation schema for the update_task_status tool, used for tool discovery and parameter validation.
    {
      name: "update_task_status",
      description:
        "Update the status of a task execution. This is typically used by workers to update task status.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The unique task execution ID",
          },
          workflowInstanceId: {
            type: "string",
            description: "The workflow instance ID",
          },
          status: {
            type: "string",
            description: "New task status",
            enum: ["IN_PROGRESS", "FAILED", "FAILED_WITH_TERMINAL_ERROR", "COMPLETED"],
          },
          output: {
            type: "object",
            description: "Task output data",
          },
          logs: {
            type: "array",
            description: "Task execution logs",
            items: {
              type: "object",
            },
          },
        },
        required: ["taskId", "workflowInstanceId", "status"],
      },
    },
  • src/index.ts:598-602 (registration)
    The request handler for listing tools, which returns the tools array containing the update_task_status tool definition, effectively registering it for discovery.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'update' implying mutation but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to existing data. The description is minimal and lacks crucial operational context for a mutation tool.

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 two sentences, front-loaded with the core purpose and followed by usage context. It's efficient with zero waste, though slightly sparse. Every sentence earns its place by adding value.

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

Completeness2/5

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

Given no annotations, no output schema, and a mutation tool with 5 parameters (including nested objects), the description is incomplete. It doesn't explain return values, error handling, or behavioral implications, leaving significant gaps for agent understanding.

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 fully documents all 5 parameters. The description adds no parameter-specific information beyond what's in the schema. Baseline is 3 since the schema does the heavy lifting, but the description doesn't compensate with additional meaning.

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?

The description clearly states the verb 'update' and resource 'status of a task execution', making the purpose evident. It distinguishes from siblings by focusing on status updates rather than creation, retrieval, or workflow control. However, it doesn't explicitly differentiate from all siblings (e.g., 'retry_workflow' might also update status).

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?

The description provides implied usage context ('typically used by workers to update task status'), suggesting it's for worker processes during task execution. However, it lacks explicit guidance on when to use this versus alternatives like 'retry_workflow' or 'terminate_workflow', and doesn't specify prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/opensensor/conductor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server