Skip to main content
Glama

create_task_definition

Create or update task definitions in Netflix Conductor Workflow Engine to manage workflow executions and troubleshooting.

Instructions

Create or update a task definition. If the task already exists, it will be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
definitionYesComplete task definition as a JSON object

Implementation Reference

  • Handler that executes the create_task_definition tool by posting the provided task definition to the Conductor API endpoint '/metadata/taskdefs' and returns a success message.
    case "create_task_definition": {
      const { definition } = args as any;
      
      await conductorClient.post("/metadata/taskdefs", [definition]);
      
      return {
        content: [
          {
            type: "text",
            text: `Task definition created/updated successfully.`,
          },
        ],
      };
    }
  • Tool schema definition for 'create_task_definition', including the input schema requiring a 'definition' object.
    {
      name: "create_task_definition",
      description:
        "Create or update a task definition. If the task already exists, it will be updated.",
      inputSchema: {
        type: "object",
        properties: {
          definition: {
            type: "object",
            description: "Complete task definition as a JSON object",
          },
        },
        required: ["definition"],
      },
    },
  • src/index.ts:598-602 (registration)
    Registration of the tools list handler, which includes the 'create_task_definition' tool in the returned tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool can create or update, implying mutation, but doesn't cover permissions required, whether updates are idempotent, what happens on conflicts, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the key action ('Create or update a task definition') and adds clarifying behavior. There's no wasted text, but it could be slightly more structured by separating creation and update scenarios for better readability.

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 the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on what a task definition includes, how to format the JSON object, what happens on success/failure, or how this integrates with sibling tools like workflows. This leaves significant gaps for an AI agent to use it correctly.

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 the single parameter 'definition' as a 'Complete task definition as a JSON object'. The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints, meeting the baseline for high schema coverage.

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 ('create or update') and resource ('task definition'), making the purpose understandable. It distinguishes from siblings like 'get_task_definition' or 'list_task_definitions' by focusing on mutation rather than retrieval. However, it doesn't specify what a 'task definition' entails or how it differs from 'workflow definition' tools, keeping it from a perfect score.

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 implies usage for creating new or updating existing task definitions, but provides no explicit guidance on when to use this versus alternatives like 'update_task_status' or 'create_workflow_definition'. It mentions the update behavior but doesn't clarify prerequisites, error conditions, or typical use cases, leaving usage somewhat ambiguous.

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