Skip to main content
Glama
JaxonDigital

Optimizely DXP MCP Server

by JaxonDigital

update_monitoring_interval

Adjust how often a monitor checks deployment status in Optimizely DXP. Set intervals from 10-600 seconds to balance urgency with API efficiency.

Instructions

⏱️ Change polling frequency for specific monitor. INSTANT: <1s. Adjusts how often monitor checks deployment status. Valid range: 10-600 seconds. Lower intervals (10-30s) for urgent deployments, higher intervals (60-300s) for long-running operations to reduce API calls. Required: monitorId, intervalSeconds. Returns updated monitor configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deploymentIdNo
intervalYes

Implementation Reference

  • Registration of the 'update_monitoring_interval' tool in the availability matrix, specifying hosting types, category, and description.
    'update_monitoring_interval': {
        hostingTypes: ['dxp-paas', 'dxp-saas', 'self-hosted', 'unknown'],
        category: 'Monitoring',
        description: 'Update monitoring interval'
  • Reference to 'update_monitoring_interval' tool in the listMonitors response, documenting it as an available command to change monitoring frequency.
    response.push('• `update_monitoring_interval` - Change monitoring frequency');
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by specifying the valid range (10-600 seconds), mentioning that changes are 'INSTANT: <1s', and noting it 'Returns updated monitor configuration'. However, it doesn't address important behavioral aspects like whether this requires special permissions, if changes are reversible, or potential rate limit implications.

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 efficiently structured with zero wasted words. It front-loads the core purpose, provides usage guidance, specifies parameters, and mentions the return value - all in four concise sentences. Every sentence adds clear value.

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

Completeness3/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 does reasonably well by explaining the action, parameters, and return value. However, it doesn't fully address the complexity of changing monitoring behavior - missing details about permissions needed, whether the change persists, or how it affects system resources. The parameter naming mismatch with the schema is also a completeness issue.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate for the schema's lack of parameter documentation. It successfully explains that 'intervalSeconds' represents 'polling frequency' with a 'Valid range: 10-600 seconds', and mentions 'monitorId' is required. However, it incorrectly names parameters as 'monitorId' and 'intervalSeconds' while the schema uses 'deploymentId' and 'interval', creating some confusion.

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 tool's purpose with a specific verb ('Change polling frequency') and resource ('for specific monitor'), distinguishing it from siblings like 'stop_monitoring' or 'get_monitoring_stats'. It goes beyond just restating the name by specifying what aspect of monitoring is being updated.

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

Usage Guidelines4/5

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

The description provides clear context for when to use different interval ranges (lower for urgent deployments, higher for long-running operations), but doesn't explicitly mention when NOT to use this tool or name specific alternatives among the sibling tools. The guidance is helpful but not exhaustive.

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