MCP tool

get_audit

Read the append-only audit trail of tenant-visible mutations: persona create/update/delete, plan approval, campaign launch/pause/resume and creative-selection changes, optimization approvals and rejections, connection updates, creative generation/revision/submission, outcome imports, audience syncs, wallet top-ups and asset charges — each with who did it, when, and the entity it touched. This is what a finance or governance reviewer asks for first. Newest first, paged.

Input

Pass fields from this schema as the tool arguments. Runtime ownership, product scope and readiness checks still apply.

Input JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "limit": {
      "description": "page size, default 50",
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "offset": {
      "description": "rows to skip, default 0",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "action": {
      "description": "filter to one action, e.g. \"campaign.launch\"",
      "type": "string"
    },
    "entity": {
      "description": "filter to one entity type, e.g. \"campaign\"",
      "type": "string"
    }
  }
}

REST mapping and authority

The tool wraps this REST endpoint. The mapping identifies path/query/body transformations and approval or idempotency headers.

Request contract

{
  "method": "GET",
  "path": "/api/v1/audit",
  "pathFields": [],
  "pathSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "pathEncoding": "encodeURIComponent for each path field",
  "governedAction": null,
  "headers": {},
  "querySchema": {
    "type": "object",
    "properties": {
      "limit": {
        "description": "page size, default 50",
        "type": "integer",
        "minimum": 1,
        "maximum": 200
      },
      "offset": {
        "description": "rows to skip, default 0",
        "type": "integer",
        "minimum": 0,
        "maximum": 9007199254740991
      },
      "action": {
        "description": "filter to one action, e.g. \"campaign.launch\"",
        "type": "string"
      },
      "entity": {
        "description": "filter to one entity type, e.g. \"campaign\"",
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "queryEncoding": "URLSearchParams; omit undefined fields, stringify supplied values",
  "responseMapping": "REST JSON is returned as MCP structuredContent and a compatibility text block; privacy-sensitive tools validate their output schema."
}

Output

This is the registered MCP output envelope. Nested fields are only modeled where the schema explicitly defines them.

Output JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {},
  "additionalProperties": {}
}

Safety annotations

MCP annotations

{
  "readOnlyHint": true,
  "destructiveHint": false,
  "idempotentHint": false,
  "openWorldHint": false
}

Annotations help a client present the tool. The API independently enforces authorization and exact action approvals. Error and retry guidance →