Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List available Medium sitemap files

medium_sitemap_index_get
Read-onlyIdempotent

List paginated Medium sitemap files by kind and return the current real file, helping you find valid sitemap URLs without guessing filenames.

Instructions

List one page of the available Medium sitemap files of one kind, with the newest real file. Requires kind.

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

Input Schema

NameRequiredDescriptionDefault
kindYesRequired. Only files of this kind. `posts` has one file per day from 2000 through the most recent day with a file.
limitNoRows per page, 1 to 500. Default: 100.
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

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 safety is covered externally. The description adds "one page" and the puzzling "with the newest real file" (never explained — presumably that the newest available file exists/appears in the listing), which is mildly useful but ambiguous; no rate-limit, ordering, or pagination-termination behavior is disclosed.

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?

A single front-loaded sentence with no filler, and the requirement is placed last where it is easy to catch. The clause "with the newest real file" is awkwardly worded and costs a little clarity.

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 six parameters and no output schema, the description should at least sketch the response shape (a page of files plus a nextCursor), especially since `cursor` references `page.nextCursor`. The core contract is conveyed, but an agent must open the schema to learn what a listing item looks like.

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 kind, limit, cursor, context, llm_model and conversation_id are all documented in the schema itself. The description only re-asserts that `kind` is required; it adds no new meaning beyond the schema, which is the expected baseline here.

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 ("List ... Medium sitemap files") plus scope ("of one kind", "one page"). It's clear enough to distinguish from pre-filtered siblings like medium_sitemap_posts_list, but it never names those siblings, leaving the differentiation implicit.

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?

The phrase "Requires `kind`" signals a necessary input, and "of one kind" hints at the filtering model, but there is no explicit statement of when to choose this over medium_sitemap_posts_list or medium_sitemap_entities_list, nor any exclusion guidance.

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