Skip to main content
Glama

List audit logs

list_audit_logs
Read-onlyIdempotent

Who changed what on the account (keys, team, webhooks, spend limit, numbers, consent, settings), newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_audit_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoActor id (exact) or part of the actor email (case-insensitive)
limitNoMax results (default 25, max 100)
actionNoOne action, or a group prefix with a trailing dot (team., api_key.)
cursorNonext_cursor from the previous page
target_typeNoTarget type, e.g. api_key, member, invite, webhook, number, phone
created_afterNoEntries at or after this time (ISO 8601)
created_beforeNoEntries at or before this time (ISO 8601); a bare date means the end of that day (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page"
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 25, max 100)"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive safety profile. The description adds useful behavioral context by stating that results are 'newest first' and by scoping the audited resource categories, though it does not discuss pagination or response shape beyond what the schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single, front-loaded sentence with no filler. Every phrase contributes to identifying the tool's domain and sort order.

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?

For a read-only filtered-list tool whose annotations and schema already carry safety, filtering, and pagination details, the description is nearly complete. It could add explicit routing versus list_events, but no critical invocation detail is missing.

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 seven filter parameters are documented in the schema. The description mentions the broad audited categories but does not add syntax or mapping details beyond what the schema already says.

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 states a precise resource and scope: account change history ('who changed what') covering keys, team, webhooks, spend limit, numbers, consent, and settings. This clearly distinguishes it from generic event or message listing siblings.

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 intended use is implied by 'who changed what on the account,' but there is no explicit when-to-use guidance, no exclusions, and no comparison to adjacent tools like list_events. The agent can infer the use case but is not routed to alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.