Skip to main content
Glama

delete_task

Delete a task from a Repsona project using its project ID and task ID. Removes the task permanently from the project management platform.

Instructions

タスクを削除します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID
taskIdYesタスクID

Implementation Reference

  • index.js:526-537 (registration)
    Tool 'delete_task' is registered in the ListToolsRequestSchema handler with its name, description, and inputSchema (requiring projectId and taskId).
    {
      name: 'delete_task',
      description: 'タスクを削除します',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'プロジェクトID' },
          taskId: { type: 'string', description: 'タスクID' },
        },
        required: ['projectId', 'taskId'],
      },
    },
  • Handler case for 'delete_task' in CallToolRequestSchema switch. Calls this.repsonaAPI.deleteTask(args.projectId, args.taskId) and returns a success message.
    case 'delete_task':
      await this.repsonaAPI.deleteTask(args.projectId, args.taskId);
      return {
        content: [
          {
            type: 'text',
            text: `タスクID ${args.taskId} が削除されました`,
          },
        ],
      };
  • RepsonaAPI.deleteTask method that makes a DELETE request to /project/{projectId}/task/{taskId} via the API.
    async deleteTask(projectId, taskId) {
      return this.makeRequest(`/project/${projectId}/task/${taskId}`, 'DELETE');
    }
Behavior2/5

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

No annotations provided, so the description carries the full burden. It does not disclose whether deletion is irreversible, requires permissions, or has side effects. Minimal beyond the verb 'delete'.

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?

One short sentence with no extraneous information. Ideal length for a simple delete operation.

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 absence of output schema and annotations, the description should explain return behavior or further guidance. It does not address what happens after deletion, leaving ambiguity.

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 coverage is 100% with descriptions for both parameters. The tool description does not add meaning beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (delete) and resource (task). It distinguishes from sibling tools like create_task or update_task.

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 on when to use this tool versus alternatives like archive_all_inbox or when not to use it. Lacks context for decision-making.

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/bellx2/repsona-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server