Configure for CDN
TheGCORE_TOOLS environment variable controls which tools are exposed. Setting GCORE_TOOLS="cdn.*" loads all CDN tools.
cdn_resources tools handle CDN resource configuration with list, create, get, update, and delete operations. The origin_groups tools manage origin server groups. The certificates tools handle SSL/TLS certificates for HTTPS delivery. The rule_templates and shields tools provide caching behavior rules and origin shielding locations. The logs and statistics tools retrieve access logs and traffic metrics. The ip_ranges tools list CDN edge IP addresses for firewall configuration.
CDN operations
Natural language requests trigger the corresponding API operations. Resource listing requires no parameters—a request like “List all my CDN resources” returns resource IDs, cnames, status, and origin group assignments. Resource creation requires the cname and origin. Requesting “Create a CDN resource for assets.example.com with origin at origin.example.com using HTTPS” provisions a new resource with the specified domain and origin configuration. The resource typically becomes active within 15 minutes after DNS propagation. Cache purging accepts resource ID and optional path patterns. A request to “Purge the cache for static.example.com” initiates a full cache purge that typically completes within 5-10 minutes. Purging specific paths uses the same tool with path parameters—“Purge /images/* from CDN resource 888473” targets the specified directory. Origin group management includes listing groups with health status and modifying group membership. Adding backup origins or adjusting health check parameters uses the origin group update tools. SSL certificate operations include listing certificates with expiration dates, creating new certificates, and associating certificates with CDN resources. Let’s Encrypt certificates can be provisioned automatically by specifying the domain. Statistics queries accept time ranges and return traffic volumes, cache hit ratios, and response code distributions. Requesting “Show traffic statistics for the last 24 hours” returns aggregated metrics across all CDN resources.Multi-step workflows
Complex CDN configurations involve multiple tools executed in sequence. Setting up a new CDN resource for a website requires creating an origin group with server addresses, creating a CDN resource pointing to that origin group, configuring SSL with a certificate, setting cache rules for static content, and updating DNS to point to the CDN endpoint. A combined request like “Set up CDN for my website with origin at 198.51.100.10, domain cdn.mysite.com, Let’s Encrypt SSL, and 24-hour cache for static files” triggers the appropriate tool sequence. Optimization workflows analyze existing configurations. A request to “Review caching configuration for resource 888473 and suggest improvements” examines current rules and identifies potential adjustments for better cache efficiency. Diagnostic workflows check resource health and configuration validity. Requesting “Check if CDN resource 888473 is properly configured and show any potential issues” validates settings and reports configuration problems.Tool naming patterns
CDN tool names follow thecdn.<resource>.<operation> pattern. The cdn.cdn_resources.list tool lists all CDN resources in the account without parameters and returns an array of resources with ID, cname, status, and origin group. The cdn.cdn_resources.create tool requires cname (the domain name) and origin_group (the origin group ID), with optional origin_protocol for HTTP or HTTPS selection. The cdn.cdn_resources.purge tool requires resource_id and accepts paths as an array of URL paths—using ["/*"] purges all content.
InfoTool parameters and behavior reflect the Gcore CDN API. Origin group configuration is documented in the origin group guide. Tool filtering options are available in the GCORE_TOOLS reference.