MisarBlog MCP Server

List subscribers

list_newsletter_subscribers

Read-onlyIdempotent

Retrieve a paginated list of newsletter subscribers for a Misar.Blog publication, using an API key to authenticate access.

Instructions

Get your newsletter subscriber list. Requires API key authentication.

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_newsletter_subscribers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv5.2.0Nov 7, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
Changed2 schema fields changedv5.1.3Oct 14, 2026
- removedInput schema / properties / limit / description
```
Removed value: -"Subscribers per page, 1-100. Defaults to 20."
```
- removedInput schema / properties / offset / description
```
Removed value: -"Subscribers to skip before this page. Defaults to 0."
```
Changed2 schema fields changedv5.1.0Aug 19, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Subscribers per page, 1-100. Defaults to 20."
```
- addedInput schema / properties / offset / description
```
Added value: +"Subscribers to skip before this page. Defaults to 0."
```
First observedv2.0.0Aug 4, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description contributes the API-key authentication requirement, which is genuinely useful additional context, but says nothing about pagination behavior, result ordering, or rate limits for what is an open-world list call.

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?

Two short sentences, front-loaded with purpose and no filler or redundancy. It is efficient, though the brevity comes at the cost of omitted pagination detail rather than being genuinely complete.

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 read-only list tool with no output schema and annotations covering safety, the description covers purpose and auth sufficiently. However, it leaves pagination — the only meaningful behavior of this tool's two parameters — entirely unexplained, which is the main gap for an agent trying to enumerate a full subscriber list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are pagination controls with 0% schema description coverage; the schema only provides types, defaults, and min/max bounds. The description does not mention pagination at all, so it fails to compensate for the coverage gap by explaining what limit and offset mean or how to page through a large subscriber list.

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 combination: retrieving the newsletter subscriber list. It is unambiguous about what is returned, though it doesn't explicitly distinguish itself from list-related siblings such as list_newsletter_issues, which could confuse an agent scanning a long tool list.

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

Usage Guidelines2/5

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

It gives no when-to-use context, no description of the alternatives for subscriber-related data, and no guidance on how or when to paginate through results. The only conditional information is a bare authentication requirement.

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