Skip to main content
Glama
thenavidm

Gumloop MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Retrieve audit logs

get_organization_audit_logs
Read-onlyIdempotent

Retrieve audit logs for all users in an organization within a specified time range to monitor activity and investigate security events.

Instructions

This endpoint retrieves audit logs for all users in an organization for a specified time period. Read operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination.
accountNoNamed private Gumloop account; selects private credentials and user/team identity.
user_idNoYour user id -- you must be an organization admin to retrieve organization logs.
end_timeYesEnd timestamp for log filtering (ISO format).
user_idsNoComma-separated list of user IDs whose events should be returned.
page_sizeNoNumber of records per page.
entity_idsNoComma-separated list of entity IDs (agents, workbooks, files) to filter by. The singular `entity_id` param accepts a single value.
start_timeYesStart timestamp for log filtering (ISO format).
event_typesNoComma-separated list of event types to filter by (e.g. `user_sign_in,credential_retrieval`). The singular `event_type` param accepts a single value.
ip_addressesNoComma-separated list of source IP addresses to filter by. The singular `ip_address` param accepts a single value.
workspace_idsNoComma-separated list of workspace (team) IDs to filter by. The singular `workspace_id` param accepts a single value.
organization_idYesThe ID of the organization to retrieve audit logs for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description's 'Read operation' merely restates the annotation and the org-wide/time-bounded scope is its only added value, which is modest against an already-rich annotation set.

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?

Two short sentences with the core purpose front-loaded and zero padding. The trailing 'Read operation' is somewhat redundant given readOnlyHint, slightly diminishing an otherwise tight statement.

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 read-only tool with full schema coverage and annotations covering safety and idempotency, the essentials are present, but the definition is thin: it omits the admin precondition, pagination expectations, and filtering capabilities that live only in the schema.

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 documented (pagination, filters, admin requirement) in the schema itself. The description adds no parameter-level meaning, so baseline 3 applies.

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?

States a specific verb (retrieves) and resource (audit logs) with scope (all users in an organization, specified time period). The name and description together make the operation unmistakable, though it doesn't distinguish itself from any sibling — which is largely unnecessary given the unrelated sibling set.

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?

No when-to-use, when-not-to-use, or alternative guidance is provided. The phrase 'for all users in an organization' hints that this is the org-wide variant, but it doesn't tell the agent when this is preferable to a user-scoped query or that admin privileges are required.

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

Deploy Server

Other Tools