Skip to main content
Glama

delete_project

Remove a project from the Things 3 task management app by marking it as canceled. Requires the project ID and authentication token.

Instructions

删除项目(通过将其标记为已取消)。需要提供项目ID和授权令牌。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes项目的ID(必需)
authTokenNo授权令牌(如未提供,将使用环境变量THINGS_AUTH_TOKEN)

Implementation Reference

  • The handler function for the delete_project tool. It retrieves the authToken, constructs parameters to set the project as canceled, builds a Things URL using buildThingsUrl('update-project'), opens the URL, and returns a success message.
    async handleDeleteProject(args) {
      const authToken = args.authToken || DEFAULT_AUTH_TOKEN;
      if (!authToken) {
        throw new Error('需要授权令牌。请设置环境变量THINGS_AUTH_TOKEN或在参数中提供authToken');
      }
    
      // 通过将 canceled 设为 true 来实现删除效果
      const params = {
        id: args.id,
        authToken,
        canceled: true,
      };
    
      const url = buildThingsUrl('update-project', params);
      await this.openThingsUrl(url);
    
      return {
        content: [
          {
            type: 'text',
            text: `🗑️ 项目已删除 (ID: ${args.id})`,
          },
        ],
      };
    }
  • Input schema for the delete_project tool, requiring 'id' and optionally 'authToken'.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: '项目的ID(必需)',
        },
        authToken: {
          type: 'string',
          description: '授权令牌(如未提供,将使用环境变量THINGS_AUTH_TOKEN)',
        },
      },
      required: ['id'],
    },
  • src/index.js:400-417 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and inputSchema for delete_project.
    {
      name: 'delete_project',
      description: '删除项目(通过将其标记为已取消)。需要提供项目ID和授权令牌。',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: '项目的ID(必需)',
          },
          authToken: {
            type: 'string',
            description: '授权令牌(如未提供,将使用环境变量THINGS_AUTH_TOKEN)',
          },
        },
        required: ['id'],
      },
    },
  • src/index.js:437-438 (registration)
    Dispatch case in the CallToolRequestSchema handler switch statement that routes to the delete_project handler.
    case 'delete_project':
      return await this.handleDeleteProject(args);
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. It states the tool marks projects as cancelled rather than physically deleting them, which is valuable behavioral context. However, it doesn't mention permissions needed beyond the auth token, whether the action is reversible, what happens to associated data, or any rate limits/constraints. For a destructive operation with zero annotation coverage, this leaves significant gaps.

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 extremely concise - just one sentence in Chinese that directly states the action, method, and required parameters. Every word earns its place with no wasted text. It's front-loaded with the core purpose immediately.

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 destructive operation with no annotations and no output schema, the description is incomplete. While it clarifies the 'mark as cancelled' behavior, it doesn't address what the tool returns, error conditions, side effects on related data, or permission requirements beyond the token. Given the complexity of a deletion operation, more contextual information would be helpful.

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 fully documents both parameters (id and authToken). The description mentions both parameters by name but adds no additional semantic meaning beyond what's in the schema descriptions. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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 project) and specifies the method ('通过将其标记为已取消' - by marking it as cancelled). It distinguishes this from a physical deletion, which is helpful context. However, it doesn't explicitly differentiate from sibling tools like 'update_project' or 'delete_todo' in terms of when to use each.

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 mentions that a project ID and authorization token are required, which provides basic prerequisites. However, it offers no guidance on when to use this tool versus alternatives like 'update_project' (which might have a status field) or other deletion tools. There's no explicit 'when' or 'when not' context provided.

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/Mieluoxxx/things_mcp'

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