Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia page pageviews

wikipedia_page_pageviews_get
Read-onlyIdempotent

Retrieve a Wikipedia page's daily or monthly pageviews by access method and agent. Provide the page title to return a view-count list for a chosen edition and date range.

Instructions

Get a Wikipedia page's daily or monthly views by access method and agent. Requires title. 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": {
      "title": "<title>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_page_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
agentNoAgent class. Default: `user`.user
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
accessNoAccess method. Default: `all-access`.all-access
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.2/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 covered. The description adds the result shape at a high level ('Returns a list') and the daily/monthly framing, but says nothing about pagination, ordering, empty-result behavior, or the per-method/per-agent breakdown format that a caller would need to interpret the list.

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 with the resource and breakdown dimensions front-loaded and zero padding. 'Returns a list' is the weakest sentence because it conveys almost nothing, but the rest earns its space.

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 10-parameter tool with no output schema, the description is thin: it does not describe what an entry in the returned list contains (timestamp, access, agent, views) and offers no guidance on the wide date window or the conversation_id handshake that the schema imposes. It is adequate to identify the tool but not complete enough to call it confidently without reading 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 enums for agent, access and granularity is already documented in the schema; the baseline of 3 applies. The description does add the framing that results are segmented by access method and agent, which ties two enum parameters to the output dimension, but adds no syntax or default detail beyond the schema.

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 names a specific verb and resource ('Get a Wikipedia page's daily or monthly views') and scopes it by access method and agent, which is enough to distinguish it from the site-level pageviews sibling even though that sibling is not named. It stops short of explicit sibling differentiation, so it is clear but not routing-grade.

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 when-to-use or when-not-to-use guidance and no alternative is named; an agent must infer from the title alone that this is the per-page variant rather than wikipedia_site_pageviews_get or wikipedia_pageviews_top_list. The only usage instruction is the prerequisite that `title` is required.

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