Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Medium daily entity URLs

medium_sitemap_entities_list
Read-onlyIdempotent

List Medium sitemap URLs for a specific day by entity kind—users, publications, tags, lists, topics, removed posts, or removed users—with cursor pagination for large result sets.

Instructions

List the user, publication, tag, list, topic, removed-post or removed-user URLs in one day's Medium sitemap. Requires kind and date. 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": {
      "kind": "<kind>",
      "date": "<date>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "medium_sitemap_entities_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesRequired. The day named by the sub-sitemap's file name (the index lists the available days).
kindYesRequired. Kind of entity sitemap: `users`, `publications`, `tags`, `lists`, `catalogs`, `topics`, `removed-posts` or `removed-users`.
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

A3.6/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. The description adds that results are URLs for a single day and that pagination uses a cursor, but it says nothing about behavior when a day/kind is unavailable or about rate limits — genuinely additive context is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero waste, and the entity scope is front-loaded ahead of the requirements and return note. Nothing repeats or meanders.

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?

For a 7-parameter read-only listing tool with no output schema, the description covers what the tool returns (entity URLs for one day) and how to page. The analytics/context parameters are self-documented in the schema, so no material gap remains, though a pointer to the index tool for valid days would have closed the loop.

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 the schema already carries full parameter meaning, including the enum for `kind` and the cursor reuse constraint. The description only restates that `kind` and `date` are required and echoes the cursor guidance rather than adding syntax, format, or defaults.

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 (List) and a precisely enumerated resource (user/publication/tag/list/topic/removed-post/removed-user URLs from a single day's Medium sitemap), which cleanly separates it from medium_sitemap_posts_list. It never names that sibling outright, so the differentiation is implied by the entity enumeration 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?

"Requires `kind` and `date`" and "one day's ... sitemap" establish the operating context, and the cursor note implies the pagination path. However, there is no explicit when-to-use/when-not guidance and no reference to medium_sitemap_index_get for discovering available days or to posts_list as the alternative.

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