OneUptime

Count Status Page Announcements

count_status_page_announcements

Read-only

Count Status Page Announcements, all or those a filter matches.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "count_status_page_announcements"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No	A field's value, or an operator such as {"_type":"GreaterThan","value":...}. Fields and operators: oneuptime_describe_resource.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / query / description

Previous value: -"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."New value: +"A field's value, or an operator such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

Changed3 schema fields changedNov 4, 2026

changedInput schema / properties / query / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / query / description

Previous value: -"Optional filter criteria. If omitted, counts all Status Page Announcements. Each field accepts a direct value (exact match) or an operator object {\"_type\": \"<Operator>\", \"value\": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {\"createdAt\": {\"_type\": \"GreaterThan\", \"value\": \"2026-01-01T00:00:00.000Z\"}}."New value: +"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

removedInput schema / properties / query / properties

Removed value: -{
-  "_id": {
-    "description": "Query operators for _id field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "attachments": {
-    "description": "Query operators for attachments field of type Entity Array. Supported operators: EqualTo, NotEqual, IsNull, NotNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "description": "Query operators for createdAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "createdByUserId": {
-    "description": "Query operators for createdByUserId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "deletedAt": {
-    "description": "Query operators for deletedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "deletedByUserId": {
-    "description": "Query operators for deletedByUserId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "description": {
-    "description": "Query operators for description field of type Markdown. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "endAnnouncementAt": {
-    "description": "Query operators for endAnnouncementAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "isOwnerNotified": {
-    "description": "Query operators for isOwnerNotified field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
-    "example": {
-      "_type": "EqualTo",
-      "value": true
-    },
-    "type": "object"
-  },
-  "monitors": {
-    "description": "Query operators for monitors field of type Entity Array. Supported operators: EqualTo, NotEqual, IsNull, NotNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "projectId": {
-    "description": "Query operators for projectId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "shouldStatusPageSubscribersBeNotified": {
-    "description": "Query operators for shouldStatusPageSubscribersBeNotified field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
-    "example": {
-      "_type": "EqualTo",
-      "value": true
-    },
-    "type": "object"
-  },
-  "showAnnouncementAt": {
-    "description": "Query operators for showAnnouncementAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "statusPages": {
-    "description": "Query operators for statusPages field of type Entity Array. Supported operators: EqualTo, NotEqual, IsNull, NotNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "subscriberNotificationStatus": {
-    "description": "Query operators for subscriberNotificationStatus field of type Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "John Doe"
-    },
-    "type": "object"
-  },
-  "subscriberNotificationStatusMessage": {
-    "description": "Query operators for subscriberNotificationStatusMessage field of type Very Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "subscriberNotificationStatusMessageOnAnnouncementUpdated": {
-    "description": "Query operators for subscriberNotificationStatusMessageOnAnnouncementUpdated field of type Very Long Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "subscriberNotificationStatusOnAnnouncementUpdated": {
-    "description": "Query operators for subscriberNotificationStatusOnAnnouncementUpdated field of type Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "John Doe"
-    },
-    "type": "object"
-  },
-  "title": {
-    "description": "Query operators for title field of type Text. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "John Doe"
-    },
-    "type": "object"
-  },
-  "updatedAt": {
-    "description": "Query operators for updatedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "version": {
-    "description": "Query operators for version field of type Number. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": 50
-    },
-    "type": "object"
-  }
-}

First observedOct 19, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing further — no statement about whether the count respects the same filters as list, whether it is subject to pagination/limits, or what it returns.

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?

It is a single short sentence with no filler, and the core scope ('all or those a filter matches') is front-loaded. It is slightly redundant with the tool name, but wastes no space.

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 one-optional-parameter read-only count with no output schema, the description is minimally adequate — the filter-syntax burden is delegated to the schema and oneuptime_describe_resource. It still lacks anything about result semantics or how counting differs from listing, which matters in a family of 80+ count_* siblings.

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 100% and the single optional 'query' parameter already explains the field/operator form and points to oneuptime_describe_resource. The description's mention of 'a filter matches' only echoes that, adding no new meaning, so baseline 3 applies.

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 verb+resource (count status page announcements) is stated, but it largely restates the tool name and title. The added clause 'all or those a filter matches' is the only information beyond the name, and it gives no differentiation from siblings like list_status_page_announcements or count_status_pages.

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 when-to-use guidance and no named alternative. An agent must infer on its own that list_status_page_announcements should be used to retrieve records and get_status_page_announcement to fetch a single one; nothing in the description routes it.

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.