Skip to main content
Glama
JaxonDigital

Optimizely DXP MCP Server

by JaxonDigital

download_logs

Download application logs from Optimizely DXP environments to local storage for offline analysis, with date filtering and background download support.

Instructions

📊 Download application logs from environment to local storage. BACKGROUND: returns immediately, download continues in background. Supports date filtering (dateFilter: "2025/10/14", "past-7-days") and log type (http, application, all). Use this when you need logs for offline analysis. For quick online analysis, use analyze_logs_streaming() instead (2x faster). Required: environment. Returns downloadId for monitoring with download_status().

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentNoProduction
logTypeNo
containerNameNoOverride default container name
slotNoDownload deployment slot logs instead of production logs. Default: false (production logs only). Set to true to get logs from /SLOTS/SLOT/ path (deployment slot logs during warmup)
dateFilterNoFilter logs by date (e.g., "2025/08/24" or "2025/08")
secondsBackNo⭐ EASIEST: Last N seconds. No date math needed! (e.g., 30)
minutesBackNo⭐ EASIEST: Last N minutes. No date math needed! (e.g., 15)
hoursBackNo⭐ EASIEST: Last N hours. No date math needed! (e.g., 6)
daysBackNo⭐ EASIEST: Last N days. No date math needed! (e.g., 7 for last week)
weeksBackNo⭐ EASIEST: Last N weeks. No date math needed! (e.g., 2)
monthsBackNo⭐ EASIEST: Last N months. No date math needed! (e.g., 3)
yearsBackNo⭐ EASIEST: Last N years. No date math needed! (e.g., 1)
startDateNoStart date (e.g., "2025/10/01"). Can use alone - endDate defaults to NOW. Format: "YYYY/MM/DD" or "YYYY-MM-DD"
endDateNoEnd date (e.g., "2025/10/08"). Can use alone - startDate defaults to 7 days before. Format: "YYYY/MM/DD" or "YYYY-MM-DD"
startDateTimeNo⚠️ ADVANCED: ISO 8601 start datetime. Can use alone - endDateTime defaults to NOW. For simpler filtering, use daysBack/hoursBack instead. (e.g., "2025-09-15T01:00:00-05:00")
endDateTimeNo⚠️ ADVANCED: ISO 8601 end datetime. Can use alone - startDateTime defaults to 7 days before. For simpler filtering, use daysBack/hoursBack instead. (e.g., "2025-09-15T01:30:00-05:00")
downloadPathNoWhere to save log files
previewOnlyNoShow download preview without actually downloading
skipConfirmationNoSkip confirmation preview (WARNING: downloads immediately without preview). Default: false - always show preview
incrementalNoUse smart incremental download (skip unchanged files). Default: true
forceFullDownloadNoForce full download even if files exist locally. Default: false
monitorNoDXP-3: Enable real-time progress monitoring during download. Shows progress updates every 10 seconds or 50 files. Default: false (opt-in)
backgroundNoDXP-3: Start download in background and return immediately with downloadId. Use download_status({ downloadId, monitor: true }) to watch progress. Default: false (blocking download)
projectNameNo
projectIdNo
apiKeyNo
apiSecretNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: asynchronous operation ('returns immediately, download continues in background'), return value ('Returns downloadId'), and monitoring requirement. It could improve by mentioning potential side effects like storage consumption or rate limits.

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?

Well-structured with emoji and clear sections, but slightly verbose with background details and sibling comparison. Every sentence adds value, but could be more streamlined. The information is front-loaded with core purpose first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Good for a complex tool with 27 parameters and no output schema. Covers purpose, usage guidelines, behavioral aspects, and references monitoring. Could be more complete by explaining output format or error conditions, but does well given the complexity.

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 78% (high), so baseline is 3. The description adds some value by explaining date filtering options and log type values, but doesn't significantly enhance understanding beyond what's already documented in the comprehensive schema descriptions.

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

Purpose5/5

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

The description clearly states the specific action ('Download application logs') and resource ('from environment to local storage'), distinguishing it from siblings like analyze_logs_streaming (online analysis) and download_status (monitoring). It provides concrete purpose beyond just the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('when you need logs for offline analysis') and when not to use ('For quick online analysis, use analyze_logs_streaming() instead'). It also mentions prerequisites ('Required: environment') and follow-up actions ('Returns downloadId for monitoring with download_status()').

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/JaxonDigital/optimizely-dxp-mcp'

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