mcp-mediawiki-crunchtools

List User Contributions Tool

list_user_contributions_tool

Read-only

Retrieve a user's MediaWiki edit history, filtered by namespace and start time, to review contributions and activity.

Instructions

List edits by a user.

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": {
      "username": "<username>"
    },
    "name": "list_user_contributions_tool"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results (default: 50, max: 500)
`username`	Yes	Username whose contributions to list
`namespace`	No	Filter by namespace (default: all)
`from_timestamp`	No	Start from this timestamp (ISO 8601)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.1Oct 22, 2026
- addedInput schema / properties / from_timestamp / description
```
Added value: +"Start from this timestamp (ISO 8601)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Filter by namespace (default: all)"
```
- addedInput schema / properties / username / description
```
Added value: +"Username whose contributions to list"
```
Changed4 schema fields changedv0.1.4Oct 1, 2026
- removedInput schema / properties / from_timestamp / description
```
Removed value: -"Start from this timestamp (ISO 8601)"
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum results (default: 50, max: 500)"
```
- removedInput schema / properties / namespace / description
```
Removed value: -"Filter by namespace (default: all)"
```
- removedInput schema / properties / username / description
```
Removed value: -"Username whose contributions to list"
```
Changed4 schema fields changedMay 4, 2026
- addedInput schema / properties / from_timestamp / description
```
Added value: +"Start from this timestamp (ISO 8601)"
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results (default: 50, max: 500)"
```
- addedInput schema / properties / namespace / description
```
Added value: +"Filter by namespace (default: all)"
```
- addedInput schema / properties / username / description
```
Added value: +"Username whose contributions to list"
```
First observedv0.1.3Mar 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

readOnlyHint=true already establishes this as a safe read, so the description's only job is to add context such as ordering, pagination, or the shape of the contribution feed. It adds none of that, leaving the behavioral picture entirely to the annotations and output schema.

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?

A single front-loaded sentence with zero padding. It is efficient, though the terseness borders on under-specification rather than optimal brevity.

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

Completeness3/5

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

With 4 parameters, an output schema, and readOnly annotations, the description only needs to explain scope and routing, and it half does. It never clarifies whether results are chronological, whether it covers all namespaces by default, or how it differs from other activity-listing siblings.

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 username, limit, namespace, and from_timestamp are all documented in the schema itself. The description contributes no additional meaning about how those filters interact, so the baseline of 3 applies.

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 ('List edits by a user'), which is enough for an agent to know this returns a user's contribution history rather than site-wide activity. It does not differentiate itself from list_recent_changes_tool or get_user_info_tool, which are the most likely confusions.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling list_recent_changes_tool that also surfaces edit activity. Usage is only inferable from the name-plus-one-sentence.

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