Skip to main content
Glama
Sign In
wikimedia

wikimedia

by deathrashed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wikipedia_list_images

Read-onlyIdempotent

Lists image titles used by a Wikipedia article, including local or non-free files. Use the results to resolve each image on Commons separately.

Instructions

List image titles used by an article; may include local/non-free files. Resolve on Commons separately. limit 1–50; continuation.imcontinue becomes cursor.

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": {
      "title": "<title>"
    },
    "name": "wikipedia_list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
titleYes
cursorNo
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond that: it warns results may include local/non-free files that must be resolved elsewhere, and explains the continuation token flow. Return format beyond 'titles' is not detailed, which keeps it from a 5.

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?

Extremely compact and front-loaded: purpose first, caveats second, parameter notes last. The telegraphic fragment style ('limit 1–50; continuation.imcontinue becomes cursor') is efficient, though slightly terse for an agent unfamiliar with the API field names.

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 no output schema and no schema descriptions, the description covers the essentials (what is listed, non-free caveat, pagination) but leaves gaps: what 'title' refers to (article title), what 'language' changes, and the shape of the returned list. Adequate but not complete for a 4-parameter 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 0% across four parameters, so the description must compensate. It does explain the cursor provenance ('continuation.imcontinue becomes cursor'), which is genuinely useful, and restates the 1–50 limit (already encoded as min/max in the schema). The 'title' and 'language' parameters get no explanation at all.

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 image titles used by an article'. The caveat that results may include local/non-free files further delimits the scope. It doesn't name a sibling tool directly, but 'Resolve on Commons separately' implicitly points to the file-resolution siblings.

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

Usage Guidelines3/5

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

'Resolve on Commons separately' implies the follow-up workflow and hints that this tool is not the place to fetch image binaries or metadata. However, no sibling is named (e.g. wikimedia_get_file, wikimedia_search_media), and there is no explicit when-not-to-use guidance.

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