Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Medium daily post URLs

medium_sitemap_posts_list
Read-onlyIdempotent

Lists Medium post URLs and last-modified dates from a specified UTC day's sitemap, returning paginated results you can continue with a cursor.

Instructions

List the post URLs and last-modified dates in one UTC day's Medium sitemap, paged with a cursor. Requires 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": {
      "date": "<date>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "medium_sitemap_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesRequired. UTC day from 1970 to 2100, `YYYY-MM-DD`, e.g. `2026-11-02`.
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.7/5.0
Behavior4/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 one thing annotations cannot: what the payload actually contains (post URLs plus last-modified dates) and that results are cursor-paged, which matters because no output schema exists.

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 sentences, front-loaded with the scope, with no filler. The trailing parenthetical '(use cursor when paginated)' is slightly redundant with the cursor parameter's own documentation, but it is not enough to count against the definition.

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 simple read-only, single-day listing tool with full schema coverage and complete annotations, the definition supplies the missing pieces: return shape and pagination model. It omits minor details like whether an empty day returns an empty list and any rate-limit expectations, which keeps it short of 5.

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%, including date format, limit bounds, and the cursor's same-filters constraint, so the schema does the heavy lifting. The description only echoes 'Requires `date`' and that a cursor exists, adding no format or behavior detail 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 names a specific verb and resource combination — listing post URLs and last-modified dates from one UTC day's Medium sitemap — which is far more precise than a restatement of the title. It does not, however, explicitly contrast itself with nearby siblings such as medium_sitemap_entities_list or medium_sitemap_index_get, so an agent must infer the boundary from the word 'posts'.

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?

It states the hard prerequisite ('Requires `date`') and the pagination follow-up ('use cursor when paginated'), which is operational guidance rather than selection guidance. There is no statement of when to prefer this over the entities or index siblings, nor any exclusion, so usage is only implied by the sitemap scope.

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