Medium Blog MCP Server

Overview Schema Source Related Servers Discussions Admin

List Sessions

list_sessions

List all blog sessions, optionally filtered by active or completed status. Use this to view existing sessions or filter by current progress.

Instructions

List all blog sessions

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`status_filter`	No	Filter by status (all, active, completed)	all

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.7/5.0

Behavior1/5

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

Annotations are absent, so the description carries the full burden of disclosing behavioral aspects like read-only nature, side effects, or authentication requirements. The description only states the action and gives no transparency about potential side effects or permissions.

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 'List all blog sessions' that is front-loaded with the primary verb and object. There is no redundant or extraneous information, making it efficient and well-structured.

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?

Given the simplicity of the tool and the presence of an output schema, the description is adequate but not thorough. It does not address edge cases like behavior with invalid filter values, pagination, or ordering, but these are not critical for a basic listing function and could be inferred from the schema or context.

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 input schema already provides a description for status_filter ('Filter by status (all, active, completed)') with 100% coverage. The tool description adds no additional meaning beyond referencing 'all' in its title, so it neither enhances nor detracts from the schema, warranting the baseline score for high coverage.

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 explicitly states 'List all blog sessions', which clearly identifies the tool's function as listing sessions. The parameter for filtering is also present in the schema, but the description itself does not fully clarify whether filtering is optional or default behavior, so it falls short of a perfect 5.

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 such as get_session_status or get_full_draft. There is no mention of scenarios where listing is preferred or how it differs from other session-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.