Mews MCP

deleteLoyaltyMemberships

Remove loyalty memberships from the Mews hospitality platform by specifying membership IDs, enabling customer program management and data cleanup.

Instructions

Deletes loyalty memberships

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "LoyaltyMembershipIds": "<LoyaltyMembershipIds>"
    },
    "name": "deleteLoyaltyMemberships"
  }
}

Input Schema

Name	Required	Description	Default
`LoyaltyMembershipIds`	Yes	Unique identifier of the loyalty memberships to be deleted

Implementation Reference

src/tools/loyalty/deleteLoyaltyMemberships.ts:22-30 (handler)

The execute function that performs the tool logic by calling the Mews API endpoint /api/connector/v1/loyaltyMemberships/delete via mewsRequest utility.

async execute(config: MewsAuthConfig, args: unknown): Promise<ToolResult> {
  const result = await mewsRequest(config, '/api/connector/v1/loyaltyMemberships/delete', args);
  return {
    content: [{
      type: 'text',
      text: JSON.stringify(result, null, 2)
    }]
  };
}

src/tools/loyalty/deleteLoyaltyMemberships.ts:8-20 (schema)

Input schema defining the required LoyaltyMembershipIds array of strings (up to 1000 items).

inputSchema: {
  type: 'object',
  properties: {
    LoyaltyMembershipIds: {
      type: 'array',
      items: { type: 'string' },
      description: 'Unique identifier of the loyalty memberships to be deleted',
      maxItems: 1000
    }
  },
  required: ['LoyaltyMembershipIds'],
  additionalProperties: false
},

src/tools/index.ts:157-169 (registration)

Registers deleteLoyaltyMembershipsTool by including it in the allTools array (used for toolMap and MCP server registration).

// Loyalty tools
getAllLoyaltyMembershipsTool,
addLoyaltyMembershipsTool,
updateLoyaltyMembershipsTool,
deleteLoyaltyMembershipsTool,
getAllLoyaltyProgramsTool,
addLoyaltyProgramsTool,
updateLoyaltyProgramsTool,
deleteLoyaltyProgramsTool,
getAllLoyaltyTiersTool,
addLoyaltyTiersTool,
updateLoyaltyTiersTool,
deleteLoyaltyTiersTool,

src/tools/index.ts:76-76 (registration)
Imports the tool definition for registration in index.ts.
```
import { deleteLoyaltyMembershipsTool } from './loyalty/deleteLoyaltyMemberships.js';
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Deletes' implies a destructive mutation, it fails to specify critical details such as whether deletion is permanent, requires specific permissions, has rate limits, or what happens to associated data. This is a significant gap for a destructive tool with zero annotation coverage.

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 extremely concise with just two words, which is efficient and front-loaded. However, this brevity borders on under-specification, as it lacks necessary details for a destructive operation. While it earns points for zero waste, it could benefit from slightly more elaboration to be fully helpful.

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 complexity of a destructive deletion tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects (e.g., irreversibility), error handling, or return values, leaving significant gaps. For such a high-stakes operation, more context is needed to ensure safe and correct usage.

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?

The schema description coverage is 100%, with the parameter 'LoyaltyMembershipIds' clearly documented as an array of unique identifiers with a max of 1000 items. The description adds no additional meaning beyond what the schema provides (e.g., no examples or edge cases). Given the high coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Deletes loyalty memberships' clearly states the action (delete) and resource (loyalty memberships), which is specific enough to understand the basic function. However, it doesn't differentiate from sibling tools like 'deleteCompanies' or 'deleteCustomers' beyond the resource name, and it lacks detail about scope (e.g., batch deletion vs. single). This makes it adequate but vague in distinguishing its specific role.

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. For example, it doesn't mention prerequisites (e.g., needing loyalty membership IDs from 'getAllLoyaltyMemberships'), exclusions (e.g., irreversible deletion), or comparisons with related tools like 'updateLoyaltyMemberships'. This absence of context leaves the agent without clear usage cues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server