Skip to main content
Glama
cristip73

MCP Server for Asana

by cristip73

asana_set_parent_for_task

Assign a parent task to organize subtasks and control their order within Asana projects for better project hierarchy management.

Instructions

Set the parent of a task and position the subtask within the other subtasks of that parent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
task_idYesThe task ID to operate on
optsNo

Implementation Reference

  • Core implementation of the tool logic: calls Asana SDK's TasksApi.setParentForTask to set the parent task.
    async setParentForTask(data: any, taskId: string, opts: any = {}) {
      const response = await this.tasks.setParentForTask({ data }, taskId, opts);
      return response.data;
    }
  • Tool dispatch handler: parses JSON strings for data/opts and calls AsanaClientWrapper.setParentForTask.
    case "asana_set_parent_for_task": {
      let { data, task_id, opts } = args;
      if ( typeof data == "string" ) {
        data = JSON.parse( data );
      }
      if ( typeof opts == "string" ) {
        opts = JSON.parse( opts );
      }
      const response = await asanaClient.setParentForTask(data, task_id, opts);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Input schema defining parameters: data (parent, insert_after/before), task_id, opts.
    export const setParentForTaskTool: Tool = {
      name: "asana_set_parent_for_task",
      description: "Set the parent of a task and position the subtask within the other subtasks of that parent",
      inputSchema: {
        type: "object",
        properties: {
          data: {
            parent: {
              type: "string",
              description: "The GID of the new parent of the task, or null for no parent",
              required: true
            },
            insert_after: {
              type: "string",
              description: "A subtask of the parent to insert the task after, or null to insert at the beginning of the list. Cannot be used with insert_before. The task must already be set as a subtask of that parent."
            },
            insert_before: {
              type: "string",
              description: "A subtask of the parent to insert the task before, or null to insert at the end of the list. Cannot be used with insert_after. The task must already be set as a subtask of that parent."
            },
          },
          task_id: {
            type: "string",
            description: "The task ID to operate on"
          },
          opts: {
            opt_fields: {
              type: "string",
              description: "Comma-separated list of optional fields to include"
            }
          }
        },
        required: ["task_id", "data"]
      }
    };
  • Tool registration: added to the exported tools array used by MCP.
    setParentForTaskTool,
  • Import of the setParentForTaskTool from task-relationship-tools.ts.
    import {
      addTaskDependenciesTool,
      addTaskDependentsTool,
      setParentForTaskTool,
      addFollowersToTaskTool
    } from './tools/task-relationship-tools.js';
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 mentions setting a parent and positioning subtasks, but fails to address critical behavioral aspects such as required permissions, whether the operation is reversible, potential side effects on task dependencies, or error conditions. This is a significant gap 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 a single, efficient sentence that front-loads the core action. It avoids unnecessary words while conveying the primary functionality, though it could benefit from additional context in subsequent sentences.

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?

For a mutation tool with 3 parameters, 33% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks essential context about behavioral traits, parameter details, error handling, and expected outcomes, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with only the 'parent' parameter documented in the schema. The description adds no information about parameters beyond what's implied by the action, failing to compensate for the low coverage. It doesn't explain the 'data' object structure, 'opts' usage, or clarify parameter interactions like 'insert_after' vs 'insert_before'.

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 clearly states the specific action ('Set the parent of a task') and includes additional functionality ('position the subtask within the other subtasks of that parent'), which distinguishes it from sibling tools like 'asana_update_task' or 'asana_create_subtask' that handle different task modifications. It uses precise verbs and specifies the resource being modified.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'asana_update_task' for general task updates or 'asana_create_subtask' for creating new subtasks. It lacks any mention of prerequisites, exclusions, or contextual cues for selection among sibling tools.

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/cristip73/mcp-server-asana'

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