Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia page history statistics

wikipedia_page_history_stats_get
Read-onlyIdempotent

Retrieve a Wikipedia page's edit count, unique editor count, and first revision to assess article history and contribution activity.

Instructions

Get a Wikipedia page's edit and editor counts plus its first revision. Requires title.

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_history_stats_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
titleYesRequired. Page title on the chosen edition, e.g. `Albert Einstein`, `C++` or `Talk:Barack Obama`. URL-encode it in the path.
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.
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's value-add is naming the returned content (edit counts, editor counts, first revision); it says nothing about rate limits, latency, or what happens for pages with no revisions, which is acceptable but not rich.

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 short sentences, front-loaded with the purpose and the returned fields. The trailing 'Requires `title`' is slightly redundant with the schema's required array, but overall there is almost no waste.

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?

There is no output schema, so the description correctly compensates by enumerating the returned fields. With annotations covering safety and the schema covering all five parameters, the definition is sufficient to call the tool, though it omits any note that results vary by edition via `lang`.

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% over five parameters, including edition codes, context, llm_model and conversation_id, so the schema carries the semantic load. The description only repeats the `title` requirement and adds no format, encoding, or edition behavior beyond the schema — the baseline 3 applies.

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 ('Get a Wikipedia page's edit and editor counts plus its first revision'), so the agent knows exactly what data comes back rather than a generic 'page history' fetch. It does not name a sibling to contrast with, so it stops short of a 5.

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?

The only guidance is the prerequisite 'Requires `title`', which is already enforced by the schema's required list. It never says when to choose this over wikipedia_page_revisions_list or wikipedia_page_get, nor any exclusions, leaving the selection decision to inference.

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