Skip to main content
Glama

delete_dashboard

Remove a dashboard from a base by providing the app token and dashboard block ID.

Instructions

Delete a dashboard from a base

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_tokenYesBase app token
dashboard_idYesDashboard block ID to delete

Implementation Reference

  • MCP tool registration and input schema for 'delete_dashboard'
      name: 'delete_dashboard',
      description: 'Delete a dashboard from a base',
      inputSchema: {
        type: 'object',
        properties: {
          app_token: {
            type: 'string',
            description: 'Base app token',
          },
          dashboard_id: {
            type: 'string',
            description: 'Dashboard block ID to delete',
          },
        },
        required: ['app_token', 'dashboard_id'],
      },
    },
  • MCP handler case for 'delete_dashboard' - calls client.deleteDashboard
    case 'delete_dashboard': {
      await client.deleteDashboard(args.app_token as string, args.dashboard_id as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              message: 'Dashboard deleted successfully',
            }, null, 2),
          },
        ],
      };
    }
  • API client method that sends DELETE request to /bitable/v1/apps/{appToken}/dashboards/{dashboardId}
    async deleteDashboard(appToken: string, dashboardId: string): Promise<void> {
      await this.request({
        method: 'DELETE',
        url: `/bitable/v1/apps/${appToken}/dashboards/${dashboardId}`,
      });
    }
  • Intent enum value for DELETE_DASHBOARD
    DELETE_DASHBOARD = 'delete_dashboard',
  • Bot handler for delete dashboard intent - calls client.deleteBlock
    private async handleDeleteDashboard(
      intent: ParsedIntent,
      context: ConversationContext,
      chatId: string
    ): Promise<void> {
      const { appToken, dashboardId } = intent.entities;
    
      if (!appToken || !dashboardId) {
        await this.sendMessage(chatId, '❓ I need both app_token and dashboard_id to delete.');
        return;
      }
    
      try {
        await this.dashboardClient.deleteBlock(appToken, dashboardId);
    
        // Clear context if this was the current dashboard
        if (context.currentDashboard?.dashboardId === dashboardId) {
          this.updateContext(context, { currentDashboard: undefined });
        }
    
        await this.sendMessage(chatId, '✅ Dashboard deleted successfully!');
    
      } catch (error: any) {
        await this.sendMessage(chatId, `❌ Failed to delete dashboard: ${error.message}`);
      }
    }
Behavior2/5

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

The description only indicates the deletion action but does not disclose behavioral traits such as whether the action is reversible, requires authorization, or has cascading effects. With no annotations, the description should provide this context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that directly states the tool's purpose. It is appropriately sized for a simple tool, though it could include one more sentence about usage without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward delete operation with two parameters, the description covers the core purpose. However, it omits context like whether the dashboard is permanently deleted or if there are dependency warnings, which would improve completeness.

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?

Input schema has 100% description coverage for both parameters, so the schema already explains their meaning clearly. The description adds no extra semantic value beyond what's in the schema, meeting the baseline.

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 the resource ('dashboard from a base'). It is specific enough to distinguish from sibling tools like create_dashboard or list_dashboards, though it could explicitly contrast with them.

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, or any prerequisites or conditions (e.g., owner permissions, inability to undo). The description 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/HypelivebytheHYPER/lark-dashboard-sdk'

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