Skip to main content
Glama

create_site_mx_record

Create MX DNS records for websites to configure mail server routing and email delivery settings.

Instructions

Creates a DNS record for a specific website. Only MX records are supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe website ID, which can be obtained by calling the [ListSites] operation.
recordNameYesThe record name.
bizNameNoThe business scenario of the record for acceleration. Leave the parameter empty if your record is not proxied. Valid values: - image_video - api - web
ttlNoThe TTL of the record. Unit: seconds. If the value is 1, the TTL of the record is determined by the system. Default: 1.
dataYesThe DNS record information. The format of this field varies based on the record type. For more information, see https://www.alibabacloud.com/help/doc-detail/2708761.html
commentNoThe comment of the record. The maximum length is 100 characters.

Implementation Reference

  • The handler function that implements the core logic of the 'create_site_mx_record' tool. It sets the DNS record type to 'MX', defaults the TTL to 1 if not provided, calls the API to create the record, and returns the result.
    export const create_site_mx_record = async (request: CallToolRequest) => {
      const req = request.params.arguments as CreateRecordRequest;
    
      req.type = 'MX';
      req.ttl = req.ttl || 1;
    
      const res = await api.createRecord(req);
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
    };
  • The schema definition for the 'create_site_mx_record' tool, including input parameters like siteId, recordName, data (with value and priority for MX), ttl, etc., and description.
    export const CREATE_SITE_MX_RECORD_TOOL: Tool = {
      name: 'create_site_mx_record',
      description:
        'Creates a DNS record for a specific website. Only MX records are supported.',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'number',
            description:
              'The website ID, which can be obtained by calling the [ListSites] operation.',
          },
          recordName: {
            type: 'string',
            description: 'The record name.',
            examples: ['www.example.com'],
          },
          bizName: {
            type: 'string',
            description:
              'The business scenario of the record for acceleration. Leave the parameter empty if your record is not proxied. Valid values:\n- image_video\n- api\n- web',
          },
          ttl: {
            type: 'number',
            description:
              'The TTL of the record. Unit: seconds. If the value is 1, the TTL of the record is determined by the system. Default: 1.',
            examples: [1],
          },
          data: {
            type: 'object',
            description:
              'The DNS record information. The format of this field varies based on the record type. For more information, see https://www.alibabacloud.com/help/doc-detail/2708761.html',
            properties: {
              value: {
                type: 'string',
                description:
                  'A valid domain name of the target mail server. Required.',
                example: ['mx.example.com'],
              },
              priority: {
                type: 'number',
                description:
                  'The priority of the record, specified within the range of 0 to 65,535. A smaller value indicates a higher priority. Required.',
              },
            },
          },
          comment: {
            type: 'string',
            description:
              'The comment of the record. The maximum length is 100 characters.',
          },
        },
        required: ['siteId', 'recordName', 'type', 'data'],
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: false,
          openWorldHint: false,
        },
      },
    };
  • Registration of the CREATE_SITE_MX_RECORD_TOOL in the ESA_OPENAPI_SITE_LIST array, which lists available site-related tools.
    export const ESA_OPENAPI_SITE_LIST = [
      LIST_SITES_TOOL,
      CREATE_SITE_TOOL,
      UPDATE_SITE_PAUSE_TOOL,
      GET_SITE_PAUSE_TOOL,
      UPDATE_RECORD_TOOL,
      CREATE_SITE_MX_RECORD_TOOL,
      CREATE_SITE_NS_RECORD_TOOL,
      CREATE_SITE_TXT_RECORD_TOOL,
      CREATE_SITE_CNAME_RECORD_TOOL,
      CREATE_SITE_A_OR_AAAA_RECORD_TOOL,
      DELETE_RECORD_TOOL,
      LIST_RECORDS_TOOL,
      GET_RECORD_TOOL,
    ];
  • Maps the 'create_site_mx_record' handler function to the esaHandlers object for tool execution dispatching.
    export const esaHandlers: ToolHandlers = {
      site_active_list,
      site_match,
      site_route_list,
      site_record_list,
      routine_create,
      routine_code_commit,
      routine_delete,
      routine_list,
      routine_get,
      routine_code_deploy,
      routine_route_list,
      deployment_delete,
      route_create,
      route_delete,
      route_update,
      route_get,
      er_record_create,
      er_record_delete,
      er_record_list,
      html_deploy,
      create_site,
      update_site_pause,
      get_site_pause,
      create_site_mx_record,
      create_site_ns_record,
      create_site_txt_record,
      create_site_cname_record,
      create_site_a_or_aaaa_record,
      update_record,
      list_records,
      get_record,
      delete_record,
      update_ipv6,
      get_ipv6,
      update_managed_transform,
      get_managed_transform,
      set_certificate,
      apply_certificate,
      get_certificate,
      delete_certificate,
      list_certificates,
      get_certificate_quota,
      list_sites,
    };
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. It states it's a creation operation but doesn't cover permissions needed, whether it's idempotent, potential side effects, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 extremely concise with just two sentences that directly state the tool's purpose and limitation. Every word earns its place, and it's front-loaded with the core functionality.

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 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, error handling, or provide context about MX records versus other DNS types. The schema covers parameters well, but behavioral and usage context is missing.

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%, so the schema already documents all 6 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, such as explaining the relationship between parameters or providing usage examples. 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 clearly states the verb ('Creates') and resource ('DNS record for a specific website'), and specifies the record type limitation ('Only MX records are supported'). However, it doesn't explicitly differentiate from sibling tools like create_site_a_or_aaaa_record or create_site_cname_record, though the MX specificity provides some implicit distinction.

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 like create_site_a_or_aaaa_record or create_site_cname_record. It doesn't mention prerequisites, such as needing a siteId from list_sites, or explain MX record use cases versus other DNS record types.

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/aliyun/mcp-server-esa'

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