Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_audit_log

Read-only

Read a Discord server's audit log to review moderation and admin activity, filtering by user, action type, target, or pagination IDs.

Instructions

Read the server audit log (needs View Audit Log). Filter by user_id, action_type, before/after. [GET /guilds/{guild_id}/audit-logs]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "guild_id": "<guild_id>"
    },
    "name": "get_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoReturn items after this ID (pagination)
limitNoMax results
beforeNoReturn items before this ID (pagination)
user_idNoUser ID
guild_idYesServer (guild) ID
target_idNoTarget ID
action_typeNoAudit log action type number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds meaningful context beyond that: the required 'View Audit Log' permission is an auth constraint an agent must verify before calling, which is exactly the kind of detail annotations cannot express.

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?

Three short fragments with the core purpose and the permission requirement front-loaded, and zero padding. The bracketed endpoint is mild noise for an agent but is compact and does convey the resource path.

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 7-parameter read tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the two things structured fields cannot: the permission gate and the filterable dimensions. Remaining gaps (pagination defaults, ordering of results) are minor given the schema already documents the pagination parameters.

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 every parameter is already documented in the input schema and the baseline is 3. The description names a subset of filters (user_id, action_type, before/after) but adds no syntax, default, or interaction detail beyond what the schema provides, and omits guild_id, target_id and limit entirely.

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 and resource ('Read the server audit log') and adds the underlying endpoint, so an agent knows exactly what data is returned. It does not differentiate against siblings, though no listed sibling appears to duplicate audit-log retrieval, so the practical ambiguity is low.

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 description gives a prerequisite ('needs View Audit Log') and lists the filter dimensions, which implies when the tool is applicable. It stops short of saying when not to use it or naming an alternative tool for related lookups, so usage is inferred rather than prescribed.

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