Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

deleteCustomers

Remove customer records from the Mews hospitality platform by specifying their IDs to manage guest data and maintain accurate customer databases.

Instructions

Deletes specified customers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CustomerIdsYesArray of customer IDs to delete

Implementation Reference

  • Complete implementation of the deleteCustomers tool, defining its name, description, input schema, and the execute handler that forwards the CustomerIds to the Mews API delete endpoint via mewsRequest utility.
    export const deleteCustomersTool: Tool = {
      name: 'deleteCustomers',
      description: 'Deletes specified customers',
      inputSchema: {
        type: 'object',
        properties: {
          CustomerIds: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of customer IDs to delete',
            maxItems: 1000
          }
        },
        required: ['CustomerIds'],
        additionalProperties: false
      },
      
      async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
        const inputArgs = args as Record<string, unknown>;
        const requestData = {
          ...inputArgs
        };
    
        const result = await mewsRequest(config, '/api/connector/v1/customers/delete', requestData);
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }]
        };
      }
    }; 
  • Registers the deleteCustomersTool by including it in the allTools array, which populates the toolMap for lookup and provides definitions for MCP server.
    deleteCustomersTool,
  • Imports the deleteCustomersTool implementation for registration in the tools index.
    import { deleteCustomersTool } from './customers/deleteCustomers.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Deletes' implies a destructive mutation, but the description doesn't specify whether deletions are permanent, reversible, require specific permissions, have rate limits, or what happens to associated data (e.g., reservations, payments). For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

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, efficient sentence with zero waste—'Deletes specified customers' is front-loaded and directly conveys the core action. Every word earns its place, making it highly concise and well-structured for quick comprehension.

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 complexity (destructive deletion), lack of annotations, and no output schema, the description is incomplete. It doesn't address critical aspects like return values, error conditions, side effects, or safety warnings. For a high-stakes operation like customer deletion, more context is needed to ensure safe and correct usage by an AI agent.

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 'CustomerIds' clearly documented as 'Array of customer IDs to delete' with a maxItems constraint. The description adds no additional parameter semantics beyond what the schema provides, such as ID format examples or deletion behavior per ID. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Deletes specified customers' clearly states the action (deletes) and resource (customers), making the purpose immediately understandable. It distinguishes from sibling tools like 'deleteCompanies' or 'deleteLoyaltyMemberships' by specifying the customer resource. However, it doesn't specify scope or constraints beyond 'specified', which keeps it from being fully specific.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., customer must exist), exclusions (e.g., cannot delete customers with active reservations), or sibling tools like 'mergeCustomers' that might be alternatives. This leaves the agent with insufficient context for appropriate selection.

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/code-rabi/mews-mcp'

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