Skip to main content
Glama
cristip73

MCP Server for Asana

by cristip73

asana_get_multiple_tasks_by_gid

Retrieve detailed information for multiple Asana tasks using their unique GIDs, supporting up to 25 tasks per request with optional field selection.

Instructions

Get detailed information about multiple tasks by their GIDs (maximum 25 tasks)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idsYesArray or comma-separated string of task GIDs to retrieve (max 25)
opt_fieldsNoComma-separated list of optional fields to include

Implementation Reference

  • Core handler function that fetches multiple tasks in parallel using Promise.all on individual getTask calls, with limit check for max 25 tasks.
    async getMultipleTasksByGid(taskIds: any, opts: any = {}) {
      const taskIdsArray = this.ensureArray(taskIds);
      
      if (taskIdsArray.length > 25) {
        throw new Error("Maximum of 25 task IDs allowed");
      }
    
      // Use Promise.all to fetch tasks in parallel
      const tasks = await Promise.all(
        taskIdsArray.map(taskId => this.getTask(taskId, opts))
      );
    
      return tasks;
    }
  • Tool dispatching handler that normalizes task_ids input (array or comma-separated string) and delegates to AsanaClientWrapper.getMultipleTasksByGid.
    case "asana_get_multiple_tasks_by_gid": {
      const { task_ids, ...opts } = args;
      // Handle both array and string input
      const taskIdList = Array.isArray(task_ids)
        ? task_ids
        : task_ids.split(',').map((id: string) => id.trim()).filter((id: string) => id.length > 0);
      const response = await asanaClient.getMultipleTasksByGid(taskIdList, opts);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Input schema definition for the tool, supporting task_ids as array (max 25 items) or comma-separated string, with optional opt_fields.
    export const getMultipleTasksByGidTool: Tool = {
      name: "asana_get_multiple_tasks_by_gid",
      description: "Get detailed information about multiple tasks by their GIDs (maximum 25 tasks)",
      inputSchema: {
        type: "object",
        properties: {
          task_ids: {
            oneOf: [
              {
                type: "array",
                items: {
                  type: "string"
                },
                maxItems: 25
              },
              {
                type: "string",
                description: "Comma-separated list of task GIDs (max 25)"
              }
            ],
            description: "Array or comma-separated string of task GIDs to retrieve (max 25)"
          },
          opt_fields: {
            type: "string",
            description: "Comma-separated list of optional fields to include"
          }
        },
        required: ["task_ids"]
      }
    };
  • Registration of all tools including getMultipleTasksByGidTool in the main tools array exported for MCP.
    export const tools: Tool[] = [
      listWorkspacesTool,
      searchProjectsTool,
      getProjectTool,
      getProjectTaskCountsTool,
      getProjectSectionsTool,
      createSectionForProjectTool,
      createProjectForWorkspaceTool,
      updateProjectTool,
      reorderSectionsTool,
      getProjectStatusTool,
      getProjectStatusesForProjectTool,
      createProjectStatusTool,
      deleteProjectStatusTool,
      searchTasksTool,
      getTaskTool,
      createTaskTool,
      updateTaskTool,
      createSubtaskTool,
      getMultipleTasksByGidTool,
      addTaskToSectionTool,
      getTasksForSectionTool,
      getProjectHierarchyTool,
      getSubtasksForTaskTool,
      getTasksForProjectTool,
      getTasksForTagTool,
      getTagsForWorkspaceTool,
      addTagsToTaskTool,
      addTaskDependenciesTool,
      addTaskDependentsTool,
      setParentForTaskTool,
      addFollowersToTaskTool,
      getStoriesForTaskTool,
      createTaskStoryTool,
      getTeamsForUserTool,
      getTeamsForWorkspaceTool,
      addMembersForProjectTool,
      addFollowersForProjectTool,
      getUsersForWorkspaceTool,
      getAttachmentsForObjectTool,
      uploadAttachmentForObjectTool,
      downloadAttachmentTool
    ];
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 maximum task limit (25). It lacks critical behavioral details: whether this is a read-only operation, authentication requirements, rate limits, error responses for invalid GIDs, or pagination. The description is minimal and misses key operational context.

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 front-loads the core purpose and includes the key constraint (maximum 25 tasks). There's no wasted verbiage or redundancy, making it appropriately concise for this tool type.

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 and no output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, how results are structured, error conditions, or authentication needs. For a tool with 2 parameters and no structured safety hints, this leaves significant gaps for an AI agent.

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 (task_ids with max 25 items and opt_fields). The description adds no additional parameter semantics beyond what's in the schema, such as examples or formatting nuances, 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 ('Get detailed information') and resource ('multiple tasks by their GIDs'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'asana_get_task' (singular) or 'asana_search_tasks', which would require a 5.

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_get_task' (for single tasks) or 'asana_search_tasks' (for filtered searches). It mentions the maximum 25 tasks but offers no context about prerequisites, error handling, or comparison to siblings.

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