Skip to main content
Glama
cristip73

MCP Server for Asana

by cristip73

asana_get_project_statuses

Retrieve all status updates for an Asana project to monitor progress and track changes over time.

Instructions

Get all status updates for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_gidYesThe project GID to get statuses for
limitNoResults per page (1-100)
offsetNoPagination offset token
opt_fieldsNoComma-separated list of optional fields to include

Implementation Reference

  • Core handler implementation: wrapper method that calls the Asana SDK's ProjectStatusesApi to fetch all status updates for a project.
    async getProjectStatusesForProject(projectId: string, opts: any = {}) {
      const response = await this.projectStatuses.getProjectStatusesForProject(projectId, opts);
      return response.data;
    }
  • Tool dispatch handler: switch case that invokes the AsanaClientWrapper method with destructured arguments and formats the response.
    case "asana_get_project_statuses": {
      const { project_gid, ...opts } = args;
      const response = await asanaClient.getProjectStatusesForProject(project_gid, opts);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool schema definition: specifies name, description, and input schema for validation.
    export const getProjectStatusesForProjectTool: Tool = {
      name: "asana_get_project_statuses",
      description: "Get all status updates for a project",
      inputSchema: {
        type: "object",
        properties: {
          project_gid: {
            type: "string",
            description: "The project GID to get statuses for"
          },
          limit: {
            type: "number",
            description: "Results per page (1-100)",
            minimum: 1,
            maximum: 100
          },
          offset: {
            type: "string",
            description: "Pagination offset token"
          },
          opt_fields: {
            type: "string",
            description: "Comma-separated list of optional fields to include"
          }
        },
        required: ["project_gid"]
      }
    };
  • Tool registration: includes the tool in the exported tools array used by the MCP server.
    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
    ];
  • Import registration: imports the tool definition for use in the handler.
      getProjectStatusTool,
      getProjectStatusesForProjectTool,
      createProjectStatusTool,
      deleteProjectStatusTool
    } from './tools/project-status-tools.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get all status updates' but doesn't describe what 'status updates' entail, whether this is a read-only operation, if it requires authentication, any rate limits, pagination behavior (implied by limit/offset parameters but not explained), or the format of returned data. This leaves significant gaps for a tool with 4 parameters and no output schema.

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 no wasted words. It's front-loaded with the core purpose and appropriately sized for what it conveys, though it could benefit from additional context.

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 tool's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'status updates' are, how results are structured, pagination behavior, or authentication needs. For a data retrieval tool with multiple parameters, this leaves too much undefined for effective agent use.

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?

The description doesn't mention any parameters beyond implying a 'project' context. However, the input schema has 100% description coverage, with clear documentation for all 4 parameters (project_gid, limit, offset, opt_fields). Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description adds no additional parameter semantics.

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 'Get all status updates for a project' clearly states the action (get) and resource (status updates for a project). It's specific enough to understand the tool's function, though it doesn't explicitly differentiate from sibling tools like 'asana_get_project_status' (singular) or 'asana_get_project' which might also provide status information.

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. It doesn't mention sibling tools like 'asana_get_project_status' (singular) or 'asana_get_project' that might overlap in functionality, nor does it specify prerequisites or contexts where this tool is preferred.

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