OneUptime

Update Alert State Timeline

update_alert_state_timeline

DestructiveIdempotent

Update one Alert State Timeline by ID: only the fields sent change. Fields: oneuptime_describe_resource.

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": {
      "id": "<id>"
    },
    "name": "update_alert_state_timeline"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID.
`startsAt`	No
`alertStateId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / id / description

Previous value: -"ID (UUID) of the Alert State Timeline to update."New value: +"ID."

Changed7 schema fields changedNov 4, 2026

removedInput schema / properties / alertStateId / description

Removed value: -"Alert State ID Relation. Which alert state does this alert change to?"

removedInput schema / properties / alertStateId / example

Removed value: -"123e4567-e89b-12d3-a456-426614174000"

changedInput schema / properties / id / description

Previous value: -"The unique identifier (UUID) of the Alert State Timeline to update. Required. Use list_alert_state_timelines to find IDs."New value: +"ID (UUID) of the Alert State Timeline to update."

removedInput schema / properties / startsAt / description

Removed value: -"When did this status change? Correct this when the recorded time is wrong - every measurement derived from this timeline is recomputed from the corrected value."

removedInput schema / properties / startsAt / example

Removed value: -{
-  "_type": "DateTime",
-  "value": "2023-10-01T12:00:00Z"
-}

addedInput schema / properties / startsAt / properties

Added value: +{
+  "_type": {
+    "enum": [
+      "DateTime"
+    ],
+    "type": "string"
+  },
+  "value": {
+    "type": "string"
+  }
+}

addedInput schema / properties / startsAt / required
```
Added value: +[
+  "_type",
+  "value"
+]
```

First observedOct 19, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, so the safety profile is known. The description adds genuine value with the partial-update rule (only supplied fields change), which is not in the annotations. However it never elaborates on the destructive behavior flagged by destructiveHint=true (what a timeline update can overwrite, e.g. startsAt/alertStateId reassignment).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and resource, which is good. But the trailing "Fields: oneuptime_describe_resource" fragment is ambiguous and reads as boilerplate rather than useful information, so not every sentence earns its place.

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 mutation with a nested object parameter, 33% schema coverage, and no output schema, the description leaves too much unstated: which fields are actually updatable, how nesting is handled, and what the destructive effect means in practice.

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

Parameters2/5

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

Schema description coverage is only 33% and only "id" is documented (as just "ID."). The description does not explain startsAt's DateTime wrapper shape or what alertStateId does, and with a nested object present under low coverage the description should compensate but does not.

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

Purpose3/5

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

The first clause is a clean specific verb+resource ("Update one Alert State Timeline by ID"), and "only the fields sent change" adds patch semantics. But the second sentence, "Fields: oneuptime_describe_resource", names a sibling tool instead of the updatable fields, muddying rather than clarifying purpose, and nothing distinguishes it from near-identical siblings like update_alert_state or update_scheduled_maintenance_state_timeline.

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?

There is no statement of when to use this versus update_alert_state, create_alert_state_timeline, or delete_alert_state_timeline, and no prerequisites or exclusions. The partial-update note implies a use case but no alternative or condition is named.

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

All OneUptime tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.