Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_list_users

Read-only

List wiki users with optional group filtering for admins, bureaucrats, or bots. Returns names, groups, edit counts, and registration dates, with active-only and pagination options.

Instructions

List wiki users with optional group filtering.

USE WHEN: User asks "who are the admins", "list all users", "show active editors".

PARAMETERS:

  • group: Filter by group - "sysop" (admins), "bureaucrat", "bot" (optional)

  • active_only: Only show recently active users (default false)

  • limit: Max users (default 50)

  • continue_from: Pagination token

RETURNS: User names, groups, edit counts, and registration dates.

Input Schema

NameRequiredDescriptionDefault
groupNoFilter by user group: 'sysop' (admins), 'bureaucrat', 'bot', or empty for all users
limitNoMaximum users to return (default 50, max 500)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
active_onlyNoOnly return users active in the last 30 days
continue_fromNoContinue token for pagination

Output Schema

NameRequiredDescriptionDefault
groupNo
usersYes
has_moreYes
total_countYes
continue_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.0
    • addedInput schema / properties / rationale
      Added value: +{
+  "description": "Optional one-sentence explanation of why you are calling this tool. Used for audit trails when present.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description supplements this with pagination behavior (continue_from token) and the return fields, but says nothing about rate limits, auth requirements, or the meaning of idempotentHint=false for retries.

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?

Header-based sections (USE WHEN / PARAMETERS / RETURNS) front-load the trigger conditions and keep each item short. There is mild duplication of schema and output-schema content, but no wasted prose.

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 an output schema present, the RETURNS line is redundant but harmless; the description covers trigger, parameters, pagination and defaults well. It is slightly incomplete on the rationale/audit parameter and on openWorld implications, which the description never addresses.

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%, and the PARAMETERS block largely restates it (group values, active_only default, limit default, continue token). It adds the parenthetical '(admins)' for sysop, but omits the rationale parameter entirely, so it neither compensates nor adds much beyond the schema baseline.

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 ('List wiki users') and adds the scoping modifier ('optional group filtering'), which distinguishes it from the user-contribution and page-listing siblings. An agent can identify it without opening the schema.

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?

The 'USE WHEN' block gives three concrete trigger phrasings ('who are the admins', 'list all users', 'show active editors') that map cleanly to the group/active_only parameters. It does not name an explicit alternative or exclusion (e.g. vs. get_user_contributions), so it stops short of a 5.

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