Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get audit log

get_audit_log
Read-only

Retrieves Discord audit log entries showing who performed which administrative action, when, and why; filter by action name, acting user, or guild to investigate past moderation events.

Instructions

Discord's historical record of administrative actions: who did what, to what, when, and why. Use this to investigate what already happened; for activity as it happens use subscribe_events. Filter by action name (like channel_create, member_ban_add, message_delete) or by the acting user. Discord merges some actions repeated in quick succession (message deletes, member moves and disconnects, channel and role reordering) into one entry that keeps only the first reason.

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": "get_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoOnly entries by this user (name or ID).
guildNoGuild (server) name or ID. Omit to use the default guild.
limitNoMax entries. Default 25.
actionNoAction name filter, like channel_delete or member_kick.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description is carrying the rest, and it contributes a genuinely important data-fidelity caveat: repeated actions are merged into one entry and only the first reason is retained, which affects how an agent should interpret results. It omits pagination behavior and any permission requirement to read the audit log, which are the remaining behavioral gaps.

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?

Four tight sentences, front-loaded with the resource definition before the alternative and then the caveat. Each sentence carries distinct information: identity, selection rule, filtering, and data-fidelity warning.

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?

With readOnlyHint covering safety and no output schema, the description supplies enough to call the tool correctly and interpret results, including the vague but useful entry shape (who/what/when/why). Only pagination and access requirements remain unaddressed for a read tool of this complexity.

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 all four parameters are already documented, and the description largely restates them while supplying additional action-name examples (channel_create, member_ban_add, message_delete) and clarifying that the user filter means the acting user. It says nothing about guild or limit, so it adds only marginal meaning over 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?

"Discord's historical record of administrative actions: who did what, to what, when, and why" names the specific resource (audit log) and its content shape, not just a tautological restatement of the title. It also explicitly distinguishes itself from subscribe_events, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

The description gives an explicit when-to-use ("investigate what already happened") paired with a named alternative and the condition that selects it ("for activity as it happens use subscribe_events"). It also sketches two filtering strategies (action name or acting user), leaving nothing essential to inference.

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