Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_query_audit_logs

Read-onlyIdempotent

Retrieve workspace audit log entries for security and compliance. Filter by event class, user, outcome, and time window.

Instructions

Query a Workspace's audit trail (Enterprise, Workspace owner only).

Retrieves audit-log rows for a class of events (applicability), optionally narrowed by user, event type, outcome, and time window. Results are timestamp-paginated: pass the last row's timestamp back as page_timestamp (with page_direction) to walk the log.

Note: Enterprise plan only — returns 403 on other plans. Additionally, only the Workspace owner's token can read audit logs; other tokens get 403.

When to Use:

  • For a security/compliance review of who did what in the Workspace.

When NOT to Use:

  • For task activity feeds — audit logs cover account/security/hierarchy administration, not per-task comment history.

Returns: A list of audit entries (event, outcome, actor, time). Use response_format json for the raw rows including every field.

Pagination: Timestamp-based. Read the timestamp of the last row, then call again with page_timestamp=<that> and page_direction="before" (older) or "after".

Examples:

  • params = {"applicability": "auth-and-security", "event_status": "failed"}

  • params = {"applicability": "user-activity", "user_emails": ["a@x.io"], "page_rows": 50}

Error Handling: 403 → not Enterprise or the token is not the Workspace owner; 400 → bad filter. Errors return an Error ... string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds critical context: Enterprise-only, workspace owner token required, pagination behavior, error codes (403, 400). No contradictions.

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 well-structured with sections (When to Use, Pagination, Examples, Error Handling) and front-loaded with purpose. It is somewhat lengthy but each section adds necessary detail. Could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of audit log queries, the description covers all essential aspects: usage context, limitations, pagination mechanics, error handling, and examples. With annotations and output schema, it is sufficiently complete for an AI agent.

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

Parameters4/5

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

While the schema provides detailed descriptions for all parameters, the description adds value by explaining pagination (page_timestamp, page_direction), giving examples, and noting the required applicability. This supplements the schema without redundancy.

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

Purpose5/5

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

The description clearly states it queries a workspace's audit trail, specific to Enterprise and workspace owner. It differentiates from sibling tools by focusing on audit logs for security/compliance, not task activity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides when to use (security/compliance review) and when not to use (task activity feeds), along with plan and ownership restrictions. This helps the agent decide appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trustxai/clickup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server