Skip to main content
Glama
code-rabi

Mews MCP

by code-rabi

updateCustomers

Modify personal details for existing customers in the Mews hospitality platform, including contact information, demographics, and identification data.

Instructions

Updates personal information of existing customers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CustomerUpdatesYesArray of customer update objects

Implementation Reference

  • The execute function implementing the core logic: parses args, sends HTTP POST to Mews API /api/connector/v1/customers/update, and returns JSON stringified result.
    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/update', requestData);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • Input schema validating an object with 'CustomerUpdates' array; each item requires 'CustomerId' and allows optional personal details.
    inputSchema: {
      type: 'object',
      properties: {
        CustomerUpdates: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              CustomerId: { type: 'string', description: 'Unique identifier of the customer to update' },
              FirstName: { type: 'string', description: 'Customer first name' },
              LastName: { type: 'string', description: 'Customer last name' },
              SecondLastName: { type: 'string', description: 'Customer second last name' },
              Title: { type: 'string', description: 'Customer title (Mr, Ms, etc.)' },
              Email: { type: 'string', description: 'Customer email address' },
              Phone: { type: 'string', description: 'Customer phone number' },
              BirthDate: { type: 'string', description: 'Customer birth date (ISO 8601)' },
              BirthPlace: { type: 'string', description: 'Customer birth place' },
              CitizenshipCountryCode: { type: 'string', description: 'ISO country code of citizenship' },
              NationalityCountryCode: { type: 'string', description: 'ISO country code of nationality' },
              GenderCode: { type: 'string', description: 'Gender code' },
              LanguageCode: { type: 'string', description: 'Preferred language ISO code' },
              LoyaltyCode: { type: 'string', description: 'Loyalty program code' },
              Occupation: { type: 'string', description: 'Customer occupation' },
              TaxIdentifier: { type: 'string', description: 'Tax identification number' }
            },
            required: ['CustomerId']
          },
          description: 'Array of customer update objects'
        }
      },
      required: ['CustomerUpdates'],
      additionalProperties: false
    },
  • Registration of the updateCustomersTool in the central allTools array exported for use in the MCP server.
    updateCustomersTool,
  • Import statement bringing the tool definition into the index for registration.
    import { updateCustomersTool } from './customers/updateCustomers.js';
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. 'Updates' implies a mutation operation, but it doesn't disclose whether this requires specific permissions, what happens to fields not included in updates (partial vs. full replacement), whether changes are reversible, or any rate limits/constraints. For a mutation tool with zero annotation coverage, this is insufficient.

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 wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place by conveying essential purpose without redundancy.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what constitutes 'personal information' beyond the schema fields, provide error handling context, describe response format, or address batch update implications (since CustomerUpdates is an array). Given the complexity of updating multiple customer records, more guidance is needed.

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%, providing detailed documentation for all parameters. The description adds minimal value beyond the schema, only implying that updates apply to 'personal information' (which aligns with fields like name, email, birth details). No additional syntax, format, or constraint details are provided beyond what's in the schema descriptions.

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 verb ('Updates') and resource ('personal information of existing customers'), making the purpose immediately understandable. It distinguishes from sibling tools like 'addCustomer' (creation) and 'deleteCustomers' (deletion), though it doesn't explicitly differentiate from 'updateCompanies' or 'mergeCustomers' which operate on different resources.

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., needing customer IDs), when not to use it (e.g., for new customers), or how it differs from related tools like 'mergeCustomers' or 'updateCompanies'. The agent must infer usage from the tool name alone.

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