Retrieve audit events for a specific user to track their activity and changes. Filter by limit, order, and archived status for precise monitoring.
Get audit events for a specific user
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| userId | Yes | ||
| orderBy | No | ||
| includeArchived | No |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.4.1Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "items": {
+ "items": {
+ "properties": {
+ "actor": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "actorId": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "countryCode": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "createdAt": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "ip": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "metadata": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "requestInformation": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "type": {
+ "type": "string"
+ },
+ "updatedAt": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "items"
+ ],
+ "type": "object"
+}v1.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds nothing beyond the annotations; it does not disclose any additional behavioral traits like pagination 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence of 7 words, which is concise but lacks essential details. It is front-loaded with purpose but sacrifices completeness for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the tool has 4 parameters and a close sibling. The description does not explain what audit events are, whether pagination is supported, or any other context, leaving the tool under-specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description does not add any meaning to the parameters. It fails to explain what 'includeArchived' or 'orderBy' entail, leaving the agent to infer from parameter names alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'audit events', specifying the scope 'for a specific user', which distinguishes it from the sibling tool `linear_getOrganizationAuditEvents`.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, such as `linear_getOrganizationAuditEvents`. There is no mention of context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tacticlaunch/mcp-linear'
If you have feedback or need assistance with the MCP directory API, please join our Discord server