Skip to main content
Glama

asana_create_project_status

Create project status updates in Asana to track progress, share updates with team members, and maintain project visibility through color-coded status 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

  • MCP tool handler case that destructures arguments and delegates to AsanaClientWrapper.createProjectStatus method.
    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) }],
      };
    }
  • Tool definition with input schema for validating arguments to asana_create_project_status.
    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"]
      }
    };
  • Tool registration by inclusion in the all_tools array, which is filtered and exported as list_of_tools for MCP.
    const all_tools: Tool[] = [
      listWorkspacesTool,
      searchProjectsTool,
      searchTasksTool,
      getTaskTool,
      createTaskTool,
      getStoriesForTaskTool,
      updateTaskTool,
      getProjectTool,
      getProjectTaskCountsTool,
      getProjectSectionsTool,
      createTaskStoryTool,
      addTaskDependenciesTool,
      addTaskDependentsTool,
      createSubtaskTool,
      getMultipleTasksByGidTool,
      getProjectStatusTool,
      getProjectStatusesForProjectTool,
      createProjectStatusTool,
      deleteProjectStatusTool,
      setParentForTaskTool,
      getTasksForTagTool,
      getTagsForWorkspaceTool,
    ];
  • Core helper method in AsanaClientWrapper that wraps the Asana SDK call to create a project status update.
    async createProjectStatus(projectId: string, data: any) {
      const body = { data };
      const response = await this.projectStatuses.createProjectStatusForProject(body, projectId);
      return response.data;
    }
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. While 'Create' implies a write operation, the description doesn't mention authentication requirements, rate limits, whether the operation is idempotent, what happens on failure, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, clear sentence that gets straight to the point with zero wasted words. It's perfectly front-loaded with the essential information and doesn't include any unnecessary elaboration or repetition. This is an excellent example of conciseness in tool descriptions.

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 creation tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the tool returns, error conditions, authentication needs, or how it fits within the broader Asana API context. The user would need to consult external documentation to understand the full operational context of this tool.

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 already documents all 6 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify semantics like what 'GID' means or how 'opt_fields' should be used. The baseline score of 3 reflects adequate but minimal value added.

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 sibling tools like 'asana_create_task_story' or 'asana_create_subtask' that also create content in Asana, leaving room for confusion about when to choose this specific creation tool.

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. With sibling tools like 'asana_get_project_status' and 'asana_delete_project_status' available, there's no indication of whether this is for initial creation versus updates, or how it relates to other project management tools in the set. The user must infer usage from the name alone.

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