Skip to main content
Glama

Daily or monthly page views for up to 5 articles in one

wiki_pageviews
Read-only

Daily or monthly page views (user agent, all access) for up to 5 articles in one Wikipedia edition over a date range of at most one year, with totals, peak day and the change between the first and second half. mode=top lists the most viewed articles of one day. Data lags by about a day; bots and unknown agents are excluded. Related tools on this server, for a different need: wiki when you need a Wikipedia page summary by title or search words, in any. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wiki_pageviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day YYYY-MM-DD (default 2 days ago)
fromNoFirst day YYYY-MM-DD (default 30 days before to); for mode=top, the day
modeNoseries (default) or top (most viewed articles of the day in from)
projectNoWikipedia edition, e.g. en.wikipedia (default), de.wikipedia
articlesNoComma list of up to 5 article titles, underscores or spaces (mode=series)
granularityNodaily (default) or monthly

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
sourceNo
projectNo
articlesNo
checkedAtNo
changeNoteNo
granularityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds real behavior beyond readOnlyHint/openWorldHint: data lags about a day, bots and unknown agents are excluded, cost is $0.002 per successful call via x402 and failed calls are free. Payment/auth mechanics are disclosed, which is valuable for a paid tool. It stops short of describing response shape or pagination, but an output schema exists.

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?

Front-loaded with the core capability and dense with useful constraints, but it is a single long paragraph mixing capability, caveats, sibling routing, and pricing, and the phrase 'in any' in the wiki sentence is garbled. Splitting pricing/lag notes from the capability sentence would improve scannability.

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?

Covers what an agent needs to call it correctly: scope limits, mode semantics, data freshness, exclusions, and cost. An output schema exists so return values need not be described. Minor gap: no note on how results behave for titles that fail to resolve or on multi-edition comparisons.

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, but the description adds meaning the schema does not: what mode=top actually returns (most viewed articles of a single day) and that the overall date range is capped at one year. Still does not clarify interactions such as how 'from' behaves when mode=top and articles are supplied together.

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+resource (daily or monthly page views), the unit of inquiry (up to 5 articles in one Wikipedia edition), the date-range cap, and the derived outputs (totals, peak day, half-over-half change). An agent can immediately distinguish it from a page-summary tool.

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?

Gives an explicit alternative and the condition that selects it: use wiki for a page summary by title or search words. It also states the operational constraints (max 5 articles, max one-year range) and explains the mode=top variant, so the agent knows which mode to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources