delete_team
Remove an existing team from TeamRetro MCP Server by specifying the team ID. Streamline team management and maintain accurate organizational structures.
Instructions
Delete an existing team
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | string |
Implementation Reference
- src/features/teams/service.ts:72-80 (handler)Core handler function that executes the team deletion by sending an HTTP DELETE request to the TeamRetro API endpoint `/v1/teams/${teamId}` and returns a success response.
async deleteTeam( teamId: string ): Promise<SingleApiResponse<any>> { await this.delete<any>(`/v1/teams/${teamId}`); return { success: true, data: {}, }; } - src/features/teams/tools.ts:68-75 (registration)Registers the 'delete_team' tool with its Zod input schema, description, and handler function that calls the service method.
delete_team: { schema: z.object({ teamId: idSchema, }), description: "Delete an existing team by its ID", handler: async (args: { teamId: string }) => createToolResponse(teamsService.deleteTeam(args.teamId)), }, - src/tools.ts:13-22 (registration)Top-level registration where teamTools (including delete_team) is spread into the main tools object used for MCP tool schema and handler generation.
const tools = { ...userTools, ...teamTools, ...teamMembersTools, ...actionTools, ...retrospectiveTools, ...agreementTools, ...healthModelTools, ...healthCheckTools, }; - src/tools.ts:24-30 (schema)Generates the JSON schema for all tools, including delete_team, from their Zod schemas for MCP protocol.
const toolSchema = Object.entries(tools).map(([name, tool]) => ({ name, description: tool.description, inputSchema: zodToJsonSchema(tool.schema, { $refStrategy: "none", }), })); - src/tools.ts:36-38 (registration)Registers the handlers for all tools, including delete_team, with error handling wrappers.
Object.entries(tools).forEach(([name, tool]) => { toolHandlers[name] = (args: any) => toolErrorHandlers(tool.handler, args); });