Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get most-viewed Wikipedia pages

wikipedia_pageviews_top_list
Read-onlyIdempotent

Retrieve a ranked list of Wikipedia pages by daily or monthly views, including non-article pages; filter by language, access method, or country.

Instructions

Get the most-viewed Wikipedia pages of a day or month, including non-article pages. Optional inputs: lang, mode, date, access and country. Returns a list.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_pageviews_top_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay (`YYYY-MM-DD`) for `mode=articles`, month (`YYYY-MM`) for `mode=countries`. Default: the latest published one, which is yesterday or last month (UTC), or the one before while that list is not out yet.
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
modeNo`articles` for the most-viewed articles (the default), `countries` for the countries that viewed the edition most.articles
accessNoAccess method. Default: `all-access`.all-access
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoCountry code. With `mode=articles`, ranks that country's articles instead of the global list.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/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 fully covered. The description adds that non-article pages are included and that the result is a list, but says nothing about freshness/lag, ordering, or result size — the date-default nuance lives only in the 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?

Two compact sentences, front-loaded with the resource and scope. 'Returns a list.' is low-value filler that could have carried ordering or format information instead, but no significant padding exists.

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 eight parameters, two enums, and no output schema, the definition is adequate because the schema does the heavy lifting on inputs. However, with no output schema the agent gets no sense of the returned list's shape (rank, article title, view count) beyond 'a list', leaving a modest completeness gap.

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 every parameter is already documented with defaults, enum options, and format examples. The description merely enumerates five of the eight parameter names and adds no syntax or behavioral detail beyond the schema, which is the expected baseline-3 outcome.

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 (most-viewed Wikipedia pages) plus the time granularity (day or month) and a scope nuance (includes non-article pages). That distinguishes it from a single-page view-count tool or a site-level aggregate, though it never names a sibling to route against. The 'including non-article pages' clause slightly conflicts with the schema's `mode=articles` wording, but intent is still recoverable.

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?

Implicitly signals usage through the mode/date dimensions and the country override, but never says when to pick this over `wikipedia_page_pageviews_get` or `wikipedia_site_pageviews_get`. No exclusions or prerequisites are stated, so the agent must infer context from the name and schema.

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