Skip to main content
Glama

LiveCRM

by ai.livecrm
OverviewDiscussionsAdmin

List Audit Events

list_audit_events
Read-only

The record of every write this deployment has made to the connected CRM, newest first: which tool wrote, what it did, how many records it touched, whether it succeeded, and whether it has already been reversed. Each entry carries the audit_event_id that reverse_audit_event takes. reversible IS THE WHOLE RULE and can be trusted: it means the write succeeded, has not been undone, and is the newest un-reversed event of its run, which is what reverse_audit_event enforces. So an entry marked reversible will be accepted and one marked otherwise would be refused. Within a run only the newest shows true; undo it and the next becomes true, so reversing a whole run is repeated newest-first rather than a guess. It covers the one connection named. 25 events by default, newest first; page with offset. Attempted-but-unresolved writes are included, which is what status is for. Optional tool narrows to one of: deduplication, assignment, mass_update, normalization, enrichment, job_change, create, write. Each event says who made it and whether an agent did; actor ('person' or 'agent') and client_id narrow to them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoOnly events written by this tool.
actorNoOnly those a person made, or only those an agent made.
limitNoHow many events to return. Defaults to 25.
offsetNoHow many to skip, for paging through older events.
client_idNoOnly those made by this agent (its OAuth client id).
connection_idYesThe CRM connection. Call list_crm_connections first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / actor
      Added value: +{
+  "description": "Only those a person made, or only those an agent made.",
+  "enum": [
+    "person",
+    "agent"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / client_id
      Added value: +{
+  "description": "Only those made by this agent (its OAuth client id).",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many events to return. Defaults to 100."New value: +"How many events to return. Defaults to 25."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), and the description adds substantial context beyond that: default page size of 25, offset paging, that it is scoped to one connection, that attempted-but-unresolved writes are included and surfaced via status, and the precise semantics of the reversible flag and how it changes after an undo. This is exactly the behavioral detail an agent needs before calling it.

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?

It is front-loaded with the core definition and each sentence carries distinct information (scope, reversible rule, pagination, status, filters). It is on the verbose side, with 'newest first' repeated and the reversible invariant given several sentences, but little is truly wasted.

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?

There is no output schema, so the description carries the return-shape burden and does so: it names the fields per entry (tool, action, record count, success, reversal status, actor type) and explains the status field for unresolved writes. Combined with the annotations, an agent has everything needed to call and interpret the result.

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 the schema already documents all six parameters, and the description largely repeats it (actor, client_id, limit default, offset paging). The one place it adds detail is the `tool` filter, but its enumerated list omits 'scoring' and 'segmentation' that the schema enum contains, an incomplete duplication rather than an enhancement. Baseline 3 fits since the schema carries the load.

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 opening clause gives a specific verb and resource ('the record of every write this deployment has made to the connected CRM, newest first') plus the exact fields returned (which tool, what it did, record count, success, reversal status). It also names the sibling it pairs with (reverse_audit_event) and the id that connects them, so an agent can distinguish it from get_audit_event_records or list_runs without opening a schema.

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

Usage Guidelines4/5

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

It clearly establishes context for use: inspecting write history, deciding whether a reversal will be accepted, and reversing a run newest-first. It explains the 'reversible' invariant in detail so the agent knows this listing is the source of truth for reverse_audit_event. It does not, however, explicitly contrast itself against siblings like get_audit_event_records or get_run_records, so there is no stated when-not-to-use.

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

All LiveCRM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources