Skip to main content
Glama
cristip73

MCP Server for Asana

by cristip73

asana_add_members_for_project

Add team members to an Asana project by specifying their user IDs and the target project ID to manage project collaboration.

Instructions

Add members to a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe project ID to add members to
membersYesArray of user GIDs to add as members to the project
opt_fieldsNoComma-separated list of optional fields to include in the response

Implementation Reference

  • Core handler that executes the tool logic: adds members to an Asana project using SDK or direct API call with fallback.
    async addMembersForProject(projectId: string, members: any) {
      try {
        const membersArray = this.ensureArray(members);
        const body = {
          data: {
            members: membersArray
          }
        };
        const response = await this.projects.addMembersForProject(body, projectId);
        return response.data;
      } catch (error: any) {
        console.error(`Error adding members to project: ${error}`);
        
        // Adăugăm mai multe detalii despre eroare pentru debugging
        if (error.response && error.response.body) {
          console.error(`Response error details: ${JSON.stringify(error.response.body, null, 2)}`);
        }
        
        // Dacă metoda standard eșuează, încercăm metoda alternativă cu callApi direct
        try {
          const client = Asana.ApiClient.instance;
          const membersArray = this.ensureArray(members);
          const response = await client.callApi(
            `/projects/${projectId}/addMembers`,
            'POST',
            { project_gid: projectId },
            {},
            {},
            {},
            { data: { members: membersArray } },
            ['token'],
            ['application/json'],
            ['application/json'],
            'Blob'
          );
          return response.data;
        } catch (fallbackError) {
          console.error("Error in fallback method for adding members:", fallbackError);
          throw fallbackError;
        }
      }
    }
  • Tool dispatch handler in switch statement that extracts parameters and calls the Asana client method.
    case "asana_add_members_for_project": {
      const { project_id, members, ...opts } = args;
      const response = await asanaClient.addMembersForProject(project_id, members);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition including input schema with project_id, members array, and opt_fields.
    export const addMembersForProjectTool: Tool = {
      name: "asana_add_members_for_project",
      description: "Add members to a project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "The project ID to add members to"
          },
          members: {
            type: "array",
            items: {
              type: "string"
            },
            description: "Array of user GIDs to add as members to the project"
          },
          opt_fields: {
            type: "string",
            description: "Comma-separated list of optional fields to include in the response"
          }
        },
        required: ["project_id", "members"]
      }
    };
  • Tool registration: imported and added to the exported tools array used by MCP server.
    addMembersForProjectTool,
    addFollowersForProjectTool,
    getUsersForWorkspaceTool,
    getAttachmentsForObjectTool,
    uploadAttachmentForObjectTool,
    downloadAttachmentTool
  • Validation helper for tool parameters: checks project_id GID and required members array.
    case 'asana_add_members_for_project':
    case 'asana_add_followers_for_project':
      result = validateGid(params.project_id, 'project_id');
      if (!result.valid) errors.push(...result.errors);
      
      const arrayParam = toolName === 'asana_add_members_for_project' ? 'members' : 'followers';
      if (!params[arrayParam]) {
        errors.push(`${arrayParam} is required`);
      }
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Add members' implies a mutation operation, but the description doesn't specify required permissions, whether this operation is idempotent, what happens if members already exist, rate limits, or what the response contains. This is a significant gap for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's appropriately sized for a straightforward operation and gets directly to the point without unnecessary elaboration.

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 inadequate. It doesn't address behavioral aspects like permissions, idempotency, or error conditions. The presence of a similar sibling tool ('asana_add_followers_for_project') creates ambiguity that the description doesn't resolve.

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 all parameters are documented in the schema. The description doesn't add any meaningful semantic context beyond what's already in the schema descriptions. It doesn't explain member vs follower distinctions, GID format expectations, or practical examples of opt_fields usage.

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 action ('Add members') and target resource ('to a project'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'asana_add_followers_for_project', which appears to serve a similar but distinct purpose in the Asana context.

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_add_followers_for_project' or other member-related operations. There's no mention of prerequisites, constraints, or typical use cases for adding members versus followers in Asana projects.

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