Reletter
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELETTER_API_KEY | Yes | Reletter API key from https://reletter.com/developers |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_publicationsA | Search for newsletters by topic, title, or author across Substack, LinkedIn, Ghost, Beehiiv and Kit. Returns subscriber numbers per publication. Specify either |
| search_issuesA | Search across the body and titles of every newsletter issue Reletter has indexed. Returns highlighted snippets when |
| autocompleteB | Returns suggested keywords and matching newsletters for a search query. |
| get_publicationA | Look up full metadata for a newsletter by its Reletter slug, e.g. 'doomberg'. Includes subscribers, engagement, social, contributors, recent issues, rankings, and SEO reach (Google search keywords and estimated traffic). |
| list_issuesA | List the 100 most recent issues for a publication in reverse chronological order. |
| get_issueA | Full data for a single issue, including the body text and the publication it belongs to. |
| contactsB | Email contacts, contact pages, and social accounts for a newsletter. Includes contributors where Reletter has identified them. |
| chart_categoriesA | List available chart platforms and categories. |
| chart_rankingsA | Latest chart rankings for a platform / category. Use chart_categories to discover valid platform and category slugs. |
| list_languagesA | List every language. Codes are used with the |
| index_statsC | Global Reletter index stats: total publications, issues, etc. |
| api_quotaA | Check your API request quota and usage for the current month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose with no overlap. For example, search_publications finds newsletters, search_issues searches within issues, and get_publication retrieves detailed metadata. No two tools could be confused.
Most tool names follow a verb_noun pattern (search_publications, get_issue, list_issues). However, 'contacts' is a noun-only name, and chart_categories/chart_rankings are noun_noun. Overall, the naming is clear and mostly consistent.
With 12 tools, the server is well-scoped for its purpose of newsletter search and metadata retrieval. Each tool serves a distinct function without being excessive.
The tool set covers the full lifecycle of querying newsletters: search (autocomplete, search_publications, search_issues), retrieval (get_publication, get_issue, list_issues, contacts), analytics (chart_rankings, index_stats), and management (api_quota). No obvious gaps exist for a read-only API.