Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia site pageviews

wikipedia_site_pageviews_get
Read-onlyIdempotent

Retrieve site-wide pageviews or unique-device totals for a Wikipedia language edition over a chosen date range, with daily or monthly granularity.

Instructions

Get a Wikipedia edition's site-wide pageviews or unique-device totals. Optional inputs: lang, metric, from, to and granularity. 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_site_pageviews_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the window as a real `YYYY-MM-DD` day (read as midnight UTC) or a full ISO 8601 date-time with a zone.
fromNoStart of the window as a real `YYYY-MM-DD` day (read as midnight UTC) or a full ISO 8601 date-time with a zone.
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
metricNo`views` (default) or `unique_devices`.views
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
granularityNo`daily` (default) or `monthly`.daily
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only 'Returns a list', with no mention of pagination, defaults, rate limits, or the conversation_id handshake the schema implies. No contradiction, but little value beyond structured fields.

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?

Three short sentences, front-loaded with the purpose before the parameter list. The closing 'Returns a list' is nearly wasted space given it conveys nothing about shape or pagination, but overall the text is lean.

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?

For a simple read-only analytics tool with full schema coverage and no output schema, the essentials are present. However, it never acknowledges the non-obvious required parameters (context, llm_model, conversation_id) or the default behaviors, which an agent must discover from the schema.

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 including lang, metric, from/to and granularity is already documented with types, defaults and enums in the schema. The description merely lists the optional parameter names without adding format or semantics. Baseline 3 applies when the schema carries the load.

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?

The description gives a specific verb and resource — retrieving site-wide pageviews or unique-device totals for a Wikipedia edition — and the word 'site-wide' implicitly separates it from the per-page sibling wikipedia_page_pageviews_get. It stops short of naming the alternative, so differentiation is inferred rather than stated.

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?

'Site-wide' hints at when to prefer this over page-level or top-list tools, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer the routing decision from the scope wording alone.

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