Skip to main content
Glama
Sign In
Medium Blog MCP Server

Medium Blog MCP Server

by Navneet1710
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Export Files

get_export_files

Retrieves all Medium blog export files for a given session ID, providing download access to each generated file.

Instructions

Retrieve all export files for download

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": {
      "session_id": "<session_id>"
    },
    "name": "get_export_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesActive session ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full responsibility for disclosing side effects. 'Retrieve' implies read-only, but there is no explicit statement about mutating state, and the output format or potential errors are not mentioned.

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?

The description is a single, concise sentence that directly states the purpose without unnecessary words or structure.

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?

For a simple retrieval tool with one parameter and no annotations, the description conveys the basic purpose. However, it lacks context about the relationship to other tools, expected output structure, or potential edge cases, making it only minimally complete.

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?

The tool description does not discuss any parameters, but the schema already provides a description for 'session_id' (Active session ID), covering 100% of parameters. Therefore, baseline of 3 applies as no additional meaning is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Retrieve' and resource 'export files' clearly specify the action and object. The purpose is unambiguous and distinct from sibling tools like 'export_to_medium' which perform export actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or typical usage scenarios such as after an export.

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