Skip to main content
Glama
cristip73

MCP Server for Asana

by cristip73

asana_create_project_status

Create project status updates in Asana to track progress, share updates, and communicate with team members using color-coded indicators.

Instructions

Create a new status update for a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_gidYesThe project GID to create the status for
textYesThe text content of the status update
colorNoThe color of the status (green, yellow, red)
titleNoThe title of the status update
html_textNoHTML formatted text for the status update
opt_fieldsNoComma-separated list of optional fields to include

Implementation Reference

  • Handler switch case for 'asana_create_project_status' that extracts parameters and delegates to AsanaClientWrapper.createProjectStatus
    case "asana_create_project_status": {
      const { project_gid, ...statusData } = args;
      const response = await asanaClient.createProjectStatus(project_gid, statusData);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Core implementation in AsanaClientWrapper that calls the Asana SDK ProjectStatusesApi.createProjectStatusForProject
    async createProjectStatus(projectId: string, data: any) {
      const body = { data };
      const response = await this.projectStatuses.createProjectStatusForProject(body, projectId);
      return response.data;
    }
  • Input schema and metadata definition for the tool
    export const createProjectStatusTool: Tool = {
      name: "asana_create_project_status",
      description: "Create a new status update for a project",
      inputSchema: {
        type: "object",
        properties: {
          project_gid: {
            type: "string",
            description: "The project GID to create the status for"
          },
          text: {
            type: "string",
            description: "The text content of the status update"
          },
          color: {
            type: "string",
            description: "The color of the status (green, yellow, red)",
            enum: ["green", "yellow", "red"]
          },
          title: {
            type: "string",
            description: "The title of the status update"
          },
          html_text: {
            type: "string",
            description: "HTML formatted text for the status update"
          },
          opt_fields: {
            type: "string",
            description: "Comma-separated list of optional fields to include"
          }
        },
        required: ["project_gid", "text"]
      }
    };
  • Import of createProjectStatusTool for registration in tools array
      getProjectStatusTool,
      getProjectStatusesForProjectTool,
      createProjectStatusTool,
      deleteProjectStatusTool
    } from './tools/project-status-tools.js';
  • Inclusion of createProjectStatusTool in the exported tools array
    createProjectStatusTool,
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. While 'Create' implies a write operation, it doesn't specify required permissions, whether the status is publicly visible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with a clear primary function and doesn't bury important 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 6 parameters and no annotations or output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns the new status object), error conditions, authentication requirements, or how this fits into Asana's project workflow. The context signals indicate this is a non-trivial tool that needs more comprehensive documentation.

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 schema description coverage is 100%, so all parameters are documented in the schema itself. The description doesn't add any additional parameter context beyond what's already in the schema (like explaining the relationship between 'text' and 'html_text', or when to use 'opt_fields'). This meets the baseline expectation when schema coverage is complete.

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 ('Create') and resource ('new status update for a project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'asana_create_task_story' or 'asana_create_project', which also create content in Asana projects.

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. There's no mention of prerequisites (e.g., needing an existing project), when not to use it, or how it differs from other creation tools in the sibling list like 'asana_create_project' or 'asana_create_task_story'.

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