Skip to main content
Glama
hybriden

Paperboy CMS

Official
by hybriden
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_audit

Read-only

Read the append-only audit log, newest first, to trace who did what, when, to which document, and from which surface.

Instructions

Read the append-only audit log, newest first: who did what (create, publish, delete, login, export…), when, to which document, from which surface (ip 'mcp' = agent). Use it to find out who changed something. Requires audit.read and a token not limited to one site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest time, ISO 8601.
fromNoEarliest time, ISO 8601, e.g. '2026-10-01T00:00:00Z'.
siteNoSite slug or id to act in (multisite). Omit to use this server's default site. Call list_sites to see what exists — an empty tree or search usually means the wrong site, not missing content.
limitNoRows to return, 1-500 (default 100).
actionNoAction prefix, e.g. 'content.' (a whole category) or 'content.publish'.
beforeNoPaging cursor: the id of the oldest row you already have.
documentIdNoOnly actions on this document.
actorUserIdNoOnly actions by this user id (from list_users).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.3
    • addedInput schema / properties / action / description
      Added value: +"Action prefix, e.g. 'content.' (a whole category) or 'content.publish'."
    • addedInput schema / properties / actorUserId / description
      Added value: +"Only actions by this user id (from list_users)."
    • addedInput schema / properties / before / description
      Added value: +"Paging cursor: the id of the oldest row you already have."
    • addedInput schema / properties / documentId / description
      Added value: +"Only actions on this document."
    • addedInput schema / properties / from / description
      Added value: +"Earliest time, ISO 8601, e.g. '2026-10-01T00:00:00Z'."
    • addedInput schema / properties / limit / description
      Added value: +"Rows to return, 1-500 (default 100)."
    • addedInput schema / properties / to / description
      Added value: +"Latest time, ISO 8601."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses the log is append-only, that results are ordered newest-first, that the actor's surface is recorded (ip 'mcp' = agent), and a non-obvious auth constraint — a token scoped to a single site cannot use it. That auth detail is exactly the kind of failure mode an agent would otherwise hit blind.

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?

Three compact sentences, front-loaded with what it returns before the use case and the auth requirement. Dense with signal and free of filler.

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 an 8-parameter read tool with no output schema, the description covers return content (actor, action, time, document, surface), ordering, and auth. Paging mechanics and default row limits are not addressed, but the schema documents those adequately.

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 baseline is 3. The description adds only indirect value: the action examples ('create, publish, delete, login, export…') hint at the vocabulary the 'action' prefix parameter expects, and 'newest first' motivates the 'before' cursor, but the cursor and limit behavior are left entirely to the schema.

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?

States a specific verb and resource ('Read the append-only audit log') plus the ordering ('newest first') and the record shape ('who did what... when, to which document, from which surface'). No sibling tool does audit-log reading, so an agent can select it unambiguously.

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?

'Use it to find out who changed something' gives a concrete triggering scenario, and the prerequisite ('Requires audit.read and a token not limited to one site') is stated explicitly. It stops short of naming an alternative or a when-not-to-use case, but no sibling offers overlapping capability.

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