Skip to main content
Glama

get_event_logs

Read-onlyIdempotent

Retrieve paginated event logs for user activities like registrations, purchases, logins, and more. Filter by user, activity type, date range, or sort order.

Instructions

🟢 READ-ONLY · Event logs · GET /v2/event-logs

Get event logs

Returns a list with all event logs of the school. The list is paginated, with a limit of 50 event logs per page. To refine the list of event logs, there are a number of query params outlined in the following section; In case more than one Query param is provided, then all of them will be applied (AND operator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoFilter by the page number. In case page number is higher than the maximum one, the results of last page will be returned
sortNoSort by creation timestamp in ascending or descending order. desc
user_idNoFilter by user id or email (encoded string)
activityNoFilter by activity name. If no activity is selected all will be applied.
created_afterNoFilter by event log creation after the given datetime (expected in UNIX timestamp format)
created_beforeNoFilter by event log creation before the given datetime (expected in UNIX timestamp format)
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral details: pagination limit of 50 per page, AND logic for multiple parameters, and the HTTP method. No contradictions with annotations.

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 reasonably concise, front-loaded with key details (read-only, pagination), though it repeats 'Get event logs' after the title. Overall, it's well-structured.

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

Completeness4/5

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

Given no output schema, the description adequately covers what is returned (list), pagination behavior, and parameter composition. It is complete for an agent to use effectively.

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 coverage is 100%, so the description adds little beyond what the schema already provides. It mentions 'query params' but does not elaborate on parameter specifics.

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 clearly states the tool retrieves event logs, is read-only, and paginated. However, it does not explicitly distinguish from potentially similar sibling tools like 'get_school_events'.

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

Usage Guidelines3/5

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

The description explains how to use query parameters (AND operator) and pagination, but lacks guidance on when to use this tool vs alternatives, such as when to choose 'get_school_events'.

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/ohneben/Learnworlds-MCP'

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