MisarBlog MCP Server

List saved articles

list_saved

Read-onlyIdempotent

Retrieve your saved articles newest first, returning paginated results with a next cursor to browse or continue through your saved reading list.

Instructions

List your saved articles, newest save first. Returns {items, next_cursor}; pass next_cursor back as cursor for the next page. Requires an API key; counts against your plan's request quota.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Page size, 1-50
`cursor`	No	next_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

Addedv5.2.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new context: the response shape {items, next_cursor}, the pagination contract, the API-key requirement, and that calls consume plan quota. It stops short of describing item structure or failure behavior (e.g., invalid/expired cursor).

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?

Three short sentences, each earning its place: what it lists first, then the return/pagination contract, then the auth and quota caveat. Front-loaded and free of filler.

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?

With no output schema, the description correctly supplies the return envelope and pagination mechanism, plus auth and quota constraints. For a simple two-optional-parameter list tool this is nearly complete; only item shape and cursor-expiry behavior are absent, which are minor.

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?

Schema coverage is 100% and both parameters already carry descriptions ('Page size, 1-50' and 'next_cursor from the previous page'). The description's cursor sentence largely restates the schema rather than adding new meaning; only the pairing of output next_cursor to input cursor adds a little. Baseline 3 is appropriate.

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?

"List your saved articles, newest save first" gives a specific verb (list), a specific resource (saved articles), and the sort order. It is clearly distinct from mutation siblings like save_article/unsave_article, but it never explicitly distinguishes itself from list_my_articles, which an agent could plausibly confuse it with.

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?

Usage is implied rather than stated: the pagination loop (pass next_cursor back as cursor) tells the agent how to continue, and the auth/quota note signals preconditions. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as search_articles for filtered lookups.

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