Skip to main content
Glama

asana_delete_project_status

Remove outdated or incorrect project status updates from Asana to maintain accurate project tracking and reporting.

Instructions

Delete a project status update

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_status_gidYesThe project status GID to delete

Implementation Reference

  • Handler function case that executes the tool: extracts project_status_gid from input arguments, calls AsanaClientWrapper.deleteProjectStatus, and returns the JSON-stringified response.
    case "asana_delete_project_status": {
      const { project_status_gid } = args;
      const response = await asanaClient.deleteProjectStatus(project_status_gid);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Defines the tool's metadata (name, description) and input schema, requiring a project_status_gid string.
    export const deleteProjectStatusTool: Tool = {
      name: "asana_delete_project_status",
      description: "Delete a project status update",
      inputSchema: {
        type: "object",
        properties: {
          project_status_gid: {
            type: "string",
            description: "The project status GID to delete"
          }
        },
        required: ["project_status_gid"]
      }
    };
  • Includes the deleteProjectStatusTool in the all_tools array, which is exported (possibly filtered) as list_of_tools for the MCP server to list available tools.
    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,
    ];
  • AsanaClientWrapper helper method that wraps the Asana SDK ProjectStatusesApi.deleteProjectStatus call, returning the response data.
    async deleteProjectStatus(statusId: string) {
      const response = await this.projectStatuses.deleteProjectStatus(statusId);
      return response.data;
    }
  • Imports the deleteProjectStatusTool from project-status-tools for inclusion in the tools list and handler dispatch.
      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?

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, has side effects (e.g., affecting project data), or error handling, which is inadequate for a destructive operation.

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, direct sentence with zero waste, front-loading the core action and resource. It's appropriately sized for a simple tool, making it easy to parse quickly.

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 destructive nature (implied by 'Delete'), lack of annotations, and no output schema, the description is incomplete. It should cover behavioral risks, permissions, or result expectations, but provides only minimal context, leaving gaps for safe 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?

Schema description coverage is 100%, with the parameter 'project_status_gid' well-documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high 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 action ('Delete') and target resource ('a project status update'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'asana_create_project_status' or 'asana_get_project_status' beyond the verb, missing explicit contrast.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid project status GID), exclusions, or related tools like 'asana_create_project_status' for creation, leaving usage context unclear.

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