Intervals.icu MCP Server

delete_events_by_date_range

Delete an athlete's Intervals.icu events for a specified date range to remove scheduled items between a start and end date.

Instructions

Delete events for an athlete from Intervals.icu in the specified date range.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "delete_events_by_date_range"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	Yes
`start_date`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 2, 2026

TDQS

C2.9/5.0

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 behavioral burden for a destructive operation. It implies deletion through the verb "Delete" but does not disclose irreversibility, whether all matching events are removed, permission requirements, or any confirmation behavior.

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?

The description is short and front-loads the action and scope before listing parameter details. The Args section is clean and earns its place by supplying the required date format.

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 destructive bulk-deletion tool with no annotations, the description is missing key context: irreversibility, scope of deletion, inclusive/exclusive date behavior, and why one would choose this over delete_event. An output schema exists, so return values need not be explained, but the operational semantics remain underspecified.

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?

The input schema has 0% description coverage and only parameter titles. The description compensates somewhat by documenting the YYYY-MM-DD format for both start_date and end_date, but it does not clarify whether the range is inclusive, how time zones are handled, or what happens if no events match.

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 uses a specific verb and resource ("Delete events") and adds the scope ("for an athlete from Intervals.icu in the specified date range"). It is clearly distinguishable from the single-event sibling delete_event, though it does not explicitly name that alternative.

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?

It states what the tool does but gives no guidance on when to use it versus delete_event, get_events, or other event-management siblings. There are no exclusions, prerequisites, or warning about bulk deletion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.