Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Wikipedia logs

wikipedia_logs_list
Read-onlyIdempotent

List public Wikipedia log events filtered by language, log type, page title, and start time, with cursor pagination for additional results.

Instructions

List public Wikipedia log events by type, page, user or time. Optional inputs: lang, type, title, since, limit and 1 more. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
typeNoOnly events of this log type.
limitNoRows per page, 1 to 500. Default: 50.
sinceNoOnly events at or after this time, as `YYYY-MM-DD` or an ISO 8601 date-time with a zone.
titleNoOnly events about this page.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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

A3.5/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 needs no restating. The description adds genuine context beyond that: results are public log events only, and pagination is cursor-based. It does not mention rate limits, result caps, or ordering, so it adds moderate rather than rich behavioral detail.

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-load purpose and then the optional inputs, with the pagination note last. The phrase "and 1 more" is wasteful and slightly confusing, but the rest is tight and earns its space.

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?

With a fully documented schema and clear annotations, the description only needs to frame purpose and returns, and it does both (returns a list, use cursor when paginated). There is no output schema, yet the cursor reference to page.nextCursor supplies enough to call iteratively; no significant gap remains.

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 enum values and the cursor's same-filters-only rule is already documented in structured fields. The description merely echoes parameter names and its "and 1 more" phrasing adds no meaning while omitting that the extra parameter is the cursor it later mentions.

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 concrete verb and resource ("List public Wikipedia log events") plus the four filter dimensions (type, page, user, time), which is more specific than the bare title. It stops short of distinguishing itself from near neighbors such as wikipedia_recent_changes_list, so an agent still has to infer which listing endpoint fits.

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?

Usage is only implied: filtering by type/page/user/time signals when the tool is appropriate, and the cursor note hints at pagination workflows. No explicit when-to-use, when-not-to-use, or named alternative (e.g. recent changes vs. log events) is given.

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