Skip to main content
Glama
olgasafonova

mediawiki-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

mediawiki_get_category_members

Read-only

Retrieve pages, subcategories, or files belonging to a specific MediaWiki category. Filter by type and paginate to explore large categories.

Instructions

Get all pages that belong to a specific category.

USE WHEN: User asks "show pages in Documentation category", "list all tutorials", "what's in Category:API".

NOT FOR: Listing categories themselves (use mediawiki_list_categories).

PARAMETERS:

  • category: Category name without "Category:" prefix (required)

  • type: Filter by type - "page", "subcat", "file", or all (default)

  • limit: Max members (default 50)

  • continue_from: Pagination token

RETURNS: Page titles in the category.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by type: 'page', 'subcat', 'file', or empty for all
limitNoMaximum members to return (default 50, max 500)
categoryYesCategory name (with or without 'Category:' prefix)
rationaleNoOptional one-sentence explanation of why you are calling this tool. Used for audit trails when present.
continue_fromNoContinue token for pagination

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
membersYes
categoryYes
has_moreYes
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

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, covering the safety profile. The description adds the pagination token concept and a default limit, but says nothing about rate limits, auth requirements, or the fact that results are capped. With annotations carrying the safety burden, this is adequate but not rich.

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?

Sectioned and front-loaded: purpose, then USE WHEN, NOT FOR, parameters, returns. Efficient, though the PARAMETERS and RETURNS blocks partially duplicate the schema and output schema respectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description need not explain return shapes, and it correctly keeps RETURNS to a single line. Usage routing, param constraints, and scoping are all present for a read-only listing tool.

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 all five params are documented structurally; the description's PARAMETERS list largely restates them. It adds the 'without Category: prefix' guidance, which actually conflicts slightly with the schema's 'with or without prefix' wording, so there is no net value gain over 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?

The first sentence states a specific verb and resource ('Get all pages that belong to a specific category') and is immediately distinguishable from mediawiki_list_categories and mediawiki_get_page. The NOT FOR line explicitly names the sibling it should not be confused with.

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?

Provides a USE WHEN block with three concrete user-phrasing examples plus an explicit NOT FOR clause naming the alternative tool. An agent has everything needed to route correctly without 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