Skip to main content
Glama
Sign In
Reletter

Reletter

Official
by getreletter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_issues

Retrieve the 100 most recent issues of any newsletter publication, listed from newest to oldest.

Instructions

List the 100 most recent issues for a publication in reverse chronological order.

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": {
      "publication_id": "<publication_id>"
    },
    "name": "list_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
publication_idYesThe Reletter publication ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description alone must disclose behavioral traits. It reveals the output is limited to 100 items and reverse chronological order, but omits authentication needs, rate limits, side effects, or return format details.

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, well-structured sentence that immediately conveys the core functionality. Every word is meaningful with zero redundant content.

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 list tool with one parameter and no output schema, the description is mostly complete. However, it weakly addresses usage context relative to sibling tools and does not mention potential pagination beyond the 100-item limit.

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 fully documents the one parameter (publication_id) with a clear description. The tool description adds no further semantic value beyond what the schema provides, so baseline of 3 is appropriate.

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 description clearly states the action (list), the resource (issues for a publication), the limit (100 most recent), and ordering (reverse chronological). It is specific and effectively distinguishes from siblings like search_issues and get_issue.

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?

The description implies the tool is for listing recent issues but does not explicitly state when to use it versus alternatives like search_issues. No exclusions or context about when not to use it are provided.

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