action1-mcp-server

Get audit records of user actions

action1_list_audit_events

Read-onlyIdempotent

Retrieve audit trail records of user actions such as logins and remote events, with filters for event type, time range, and keywords to review activity or investigate incidents.

Instructions

Get audit records of user actions. 'The Audit Trail contains event records associated with user actions, such as logins, remote. Perm: view_audit.

Input Schema

Name	Required	Description
`from`	No	Provide the number of the first record to be returned.
`event`	No	The list of comma-separated event names to include.
`limit`	No	Set the maximum number of items to be returned (the page size).
`cursor`	No	next_cursor of the previous call; takes precedence over from.
`filter`	No	Provide a case-insensitive substring to filter and narrow down returned results (i.e., if...
`sortby`	No	Define the sorting order by a certain field.
`timeto`	No	The end date and time in the following format: YYYY-MM-DD_HH-MM-SS
`from_id`	No	Provide the sequential ID of the first record to be returned.
`verbose`	No	Skip per-item compactor.
`timefrom`	No	The start date and time in the following format: YYYY-MM-DD_HH-MM-SS
`auto_paginate`	No	Walk pages until limit or the size budget; then continue with next_cursor.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`total`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / auto_paginate / description

Previous value: -"Walk all pages."New value: +"Walk pages until limit or the size budget; then continue with next_cursor."

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor."New value: +"next_cursor of the previous call; takes precedence over from."

addedInput schema / properties / from / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / from / minimum
```
Added value: +0
```
addedInput schema / properties / limit / maximum
```
Added value: +50000
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

removedInput schema / properties / timefrom / format
```
Removed value: -"date-time"
```

addedInput schema / properties / timefrom / pattern

Added value: +"^(?:\\d{4}-\\d{2}-\\d{2}_\\d{2}-\\d{2}-\\d{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+-]\\d{2}:?\\d{2}))$"

removedInput schema / properties / timeto / format
```
Removed value: -"date-time"
```

addedInput schema / properties / timeto / pattern

Added value: +"^(?:\\d{4}-\\d{2}-\\d{2}_\\d{2}-\\d{2}-\\d{2}|\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+-]\\d{2}:?\\d{2}))$"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "description": {},
+  "details": {},
+  "event": {},
+  "id": {},
+  "object_name": {},
+  "object_url": {},
+  "org_id": {},
+  "org_name": {},
+  "self": {},
+  "status_message": {},
+  "timestamp": {},
+  "type": {},
+  "user_id": {},
+  "user_name": {}
+}

First observedv0.5.0Jun 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already declare this is a read-only, idempotent, non-destructive, open-world operation. The description adds the useful auth requirement 'view_audit' and gives event examples such as logins, but it does not add much beyond that about pagination behavior, result scope, 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.

Conciseness3/5

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

The purpose is front-loaded and the description is short, but the second sentence is an awkward quoted fragment ending in an incomplete 'remote.' It is concise overall, yet the structure and clarity are not clean enough for a higher score.

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?

The tool has 12 optional parameters, rich schema descriptions, annotations, and an output schema, so the description need not repeat every detail. However, for a complex audit-log query tool it is thin on when to use it versus alternatives and on practical querying guidance, making it only minimally complete.

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%, so all 12 parameters are already documented in the schema. The description only loosely hints at event types with 'logins, remote' and does not add syntax or filtering semantics beyond what the schema provides, so the baseline 3 is appropriate.

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 states a clear verb and resource: getting audit records of user actions. It is understandable despite the awkward quoted fragment, but it does not explicitly distinguish this list/query tool from sibling audit tools such as action1_get_audit_event, action1_audit_log_search, or action1_export_audit_log.

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 provides a permission requirement ('Perm: view_audit') but no guidance on when to use this tool versus related audit tools. There are no exclusions, alternatives, or scenario cues to help an agent choose correctly among the audit-log siblings.

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

Deploy Server