Skip to main content
Glama

asana_add_task_dependents

Add dependent tasks to an Asana task to establish workflow dependencies and manage task sequencing within projects.

Instructions

Set dependents for a task (tasks that depend on this task)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID to add dependents to
dependentsYesArray of task IDs that depend on this task

Implementation Reference

  • The main handler for the 'asana_add_task_dependents' tool. Extracts arguments and calls the Asana client wrapper to add dependents to a task.
    case "asana_add_task_dependents": {
      const { task_id, dependents } = args;
      const response = await asanaClient.addTaskDependents(task_id, dependents);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines the input schema, name, and description for the 'asana_add_task_dependents' tool.
    export const addTaskDependentsTool: Tool = {
      name: "asana_add_task_dependents",
      description: "Set dependents for a task (tasks that depend on this task)",
      inputSchema: {
        type: "object",
        properties: {
          task_id: {
            type: "string",
            description: "The task ID to add dependents to"
          },
          dependents: {
            type: "array",
            items: {
              type: "string"
            },
            description: "Array of task IDs that depend on this task"
          }
        },
        required: ["task_id", "dependents"]
      }
    };
  • Implements the core logic to add dependents to a task using the Asana SDK TasksApi.addDependentsForTask.
    async addTaskDependents(taskId: string, dependents: string[]) {
      const body = {
        data: {
          dependents: dependents
        }
      };
      const response = await this.tasks.addDependentsForTask(body, taskId);
      return response.data;
    }
  • Imports the tool schema for registration in the tool handler.
    import {
      addTaskDependenciesTool,
      addTaskDependentsTool,
      setParentForTaskTool
    } from './tools/task-relationship-tools.js';
  • Registers the tool in the all_tools array used for MCP tool listing.
    addTaskDependenciesTool,
    addTaskDependentsTool,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose permissions needed, whether this overwrites or appends dependents, error conditions, or rate limits, leaving significant gaps 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every part contributing essential information.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, return values, error handling, and usage context, which are critical for an AI agent to invoke 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 fully documents both parameters. The description adds no additional meaning beyond what the schema provides, such as format examples or edge cases, 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 ('Set') and resource ('dependents for a task'), specifying that it adds tasks that depend on the given task. It distinguishes from sibling 'asana_add_task_dependencies' by focusing on dependents rather than dependencies, but doesn't explicitly contrast them.

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?

No guidance on when to use this tool versus alternatives like 'asana_add_task_dependencies' or 'asana_update_task'. The description implies usage for setting dependents but lacks context about prerequisites, constraints, or typical scenarios.

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

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