Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Medium publication posts

medium_publication_posts_list
Read-onlyIdempotent

List the ten newest posts from a Medium publication by slug or custom domain, with an optional tag filter to find relevant recent articles.

Instructions

List a publication's ten newest Medium posts by Medium slug or its own domain, optionally filtered by tag. Requires slug. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOnly posts of the publication carrying this tag (medium.com publications only; not supported on a custom domain).
slugYesRequired. Medium publication slug (`netflix-techblog`) or its own domain (`uxdesign.cc`).
domainNoThe publication's own domain (`uxdesign.cc`), when it runs on one. Overrides the slug.
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 cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds a genuinely useful behavioral fact beyond them: results are capped at the ten newest posts, which signals there is no pagination or full-history access. It does not address failure modes (e.g. a slug resolving to a custom-domain publication).

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?

Three short sentences, front-loaded with the scope and the ten-post cap before the requirement. Slight redundancy between "by Medium slug or its own domain" and the following "Requires `slug`," and "Returns a list" is thin but does partially substitute for the missing output schema.

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 low-complexity read-only list tool whose annotations and schema are rich, the definition covers identifier choice, the tag filter, the result cap, and the return shape. The remaining gap is that with no output schema it does not say what fields each post carries, so an agent cannot anticipate the response items.

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 documents slug, domain, tag, context, llm_model, and conversation_id. The description restates slug as required and the tag filter as optional but adds no syntax or format detail beyond that, which is the correct baseline when the schema does the work.

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 states a specific verb and resource ("List a publication's ten newest Medium posts") and names both accepted identifiers (Medium slug or own domain) plus the optional tag filter. It is clearly distinguishable from author/tag/sitemap listing siblings by the 'publication' anchor, though no sibling is named explicitly.

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: the tag filter is described as optional, and the slug/domain choice is mentioned, but there is no guidance on when to prefer this over medium_author_posts_list, medium_tag_posts_list, or medium_sitemap_posts_list. The domain-overrides-slug relationship is left to the schema to explain.

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