Skip to main content
Glama

update_managed_transform

Modify managed transform configurations for your website to control client geolocation and IP address headers in origin requests.

Instructions

Modifies the configuration of managed transforms for your website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe website ID, which can be obtained by calling the ListSites operation.
addClientGeolocationHeaderNoSpecifies whether to include the header that indicates the geographical location of a client in an origin request.
siteVersionNoThe version number of the website. You can use this parameter to specify a version of your website to apply the feature settings. By default, version 0 is used.
addRealClientIpHeaderNoSpecifies whether to include the 'ali-real-client-ip' header that indicates the 's real IP address in an origin request.
realClientIpHeaderNameNoThe actual client IP header name.

Implementation Reference

  • The primary handler function for the MCP tool 'update_managed_transform'. It receives the tool call request, invokes the API service, and returns the response as tool output.
    export const update_managed_transform = async (request: CallToolRequest) => {
      const res = await api.updateManagedTransform(
        request.params.arguments as UpdateManagedTransformRequest,
      );
    
      return {
        content: [{ type: 'text', text: JSON.stringify(res) }],
        success: true,
      };
    };
  • The tool metadata and input schema definition for 'update_managed_transform', including properties, required fields, and annotations.
    export const UPDATE_MANAGED_TRANSFORM_TOOL: Tool = {
      name: 'update_managed_transform',
      description:
        'Modifies the configuration of managed transforms for your website.',
      inputSchema: {
        type: 'object',
        properties: {
          siteId: {
            type: 'number',
            description:
              'The website ID, which can be obtained by calling the ListSites operation.',
            example: [12228828888],
          },
          addClientGeolocationHeader: {
            type: 'string',
            description:
              'Specifies whether to include the header that indicates the geographical location of a client in an origin request.',
            enum: ['on', 'off'],
          },
          siteVersion: {
            type: 'number',
            description:
              'The version number of the website. You can use this parameter to specify a version of your website to apply the feature settings. By default, version 0 is used.',
            example: [0],
          },
          addRealClientIpHeader: {
            type: 'string',
            description:
              "Specifies whether to include the 'ali-real-client-ip' header that indicates the 's real IP address in an origin request.",
            enum: ['on', 'off'],
          },
          realClientIpHeaderName: {
            type: 'string',
            description: 'The actual client IP header name.',
            example: ['test_header'],
          },
        },
        required: ['siteId'],
        annotations: {
          readOnlyHint: false,
          destructiveHint: false,
          idempotentHint: false,
        },
      },
    };
  • Registration of the 'update_managed_transform' tool (via UPDATE_MANAGED_TRANSFORM_TOOL) in the MANAGED_TRANSFORM_LIST array, which is later included in the full ESA_OPENAPI_LIST.
    export const MANAGED_TRANSFORM_LIST = [
      UPDATE_MANAGED_TRANSFORM_TOOL,
      GET_MANAGED_TRANSFORM_TOOL,
    ];
  • Registration of the handler function 'update_managed_transform' in the esaHandlers map, mapping tool names to their handler implementations.
    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,
    };
  • Supporting API wrapper method in the service client that wraps the Alibaba Cloud ESA updateManagedTransform API call, used by the tool handler.
    updateManagedTransform(params: UpdateManagedTransformRequest) {
      const request = new UpdateManagedTransformRequest(params);
      return this.callApi(
        this.client.updateManagedTransform.bind(this.client) as ApiMethod<
          UpdateManagedTransformRequest,
          UpdateManagedTransformResponse
        >,
        request,
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Modifies' implies mutation, it doesn't disclose whether this requires specific permissions, what happens to existing settings not mentioned, whether changes are reversible, or any rate limits. For a configuration 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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 configuration mutation tool with 5 parameters and no annotations or output schema, the description is insufficient. It doesn't explain what 'managed transforms' are, what the expected response looks like, error conditions, or provide any context about the broader system. The agent would need to guess about important behavioral aspects.

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%, meaning all parameters are documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions. The baseline score of 3 reflects adequate coverage through the schema alone.

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 ('Modifies') and target ('configuration of managed transforms for your website'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from potential siblings like 'get_managed_transform' or other update tools, which would require explicit comparison.

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. There's no mention of prerequisites (like needing to first get managed transforms), when this operation is appropriate, or what distinguishes it from other configuration tools in the sibling list.

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