Skip to main content
Glama
cappyeo

discord-mcp

audit_log_get

Read-onlyIdempotent

Retrieve Discord server audit logs to investigate actions like member kicks, with optional filters for user, action type, and pagination.

Instructions

Purpose: Fetch audit log entries for a guild.

When to use: investigate "who kicked X?", post-incident forensics.

Example: {guild_id:"999000999000999000", limit:50, action_type:20} (action_type 20 = MEMBER_KICK)

Pagination: pass before as the last entry's oldest_id to fetch older entries. Discord returns entries in descending ID order; repeat until a page is empty.

Returns: {entries:[{id, target_id, user_id, action_type, reason}], count, oldest_id?}. Structured reason values remain raw moderator-controlled data; the human-readable text response fences them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax entries (1-100, default 50)
beforeNoReturn entries with ID less than this entry ID
user_idNoFilter to entries triggered by this user
guild_idYesGuild to query
action_typeNoFilter by Discord audit action type

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds useful context beyond them: pagination via the `before`/`oldest_id` relationship, descending ID ordering, and the note that `reason` values are raw moderator-controlled data. It stops short of covering rate limits or permission requirements, but the safety profile is already well established.

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?

The description is well-structured with bold headers and is free of filler. Purpose, usage context, example, pagination, and return contract are each one concise section, making it easy for an agent to parse quickly and call the tool correctly.

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?

Given the rich schema, annotations, and output schema, the description covers the essential operational details: purpose, when to use, concrete example, pagination behavior, and return shape. It could mention the 'View Audit Log' permission requirement, but that is a minor gap for a read-only call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 a concrete example mapping `action_type:20` to MEMBER_KICK and explains how the `before` parameter connects to the return field `oldest_id`, which is more meaningful than the schema's generic 'ID less than' description.

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 description explicitly states 'Fetch audit log entries for a guild' with a specific verb and resource. This distinguishes it from all sibling tools, none of which target audit logs, and the 'when to use' examples reinforce its unique forensic purpose.

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?

A dedicated 'When to use' section gives clear investigative use cases like 'who kicked X?' and post-incident forensics. It does not explicitly mention when not to use the tool or name alternatives, but the context is strong enough for an agent to select it appropriately.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cappyeo/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server