Skip to main content
Glama
Sign In
markpin-mcp

markpin-mcp

by mud-studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List recent pages

list_recent
Read-only

List recently updated saved pages newest first, or set bookmarked=true to see bookmarked pages newest bookmark first.

Instructions

Lists the most recently updated pages, newest first. With bookmarked=true, lists pages with a reading bookmark, newest bookmark first.

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

Input Schema

NameRequiredDescriptionDefault
nNoHow many pages to return. Default 20.
bookmarkedNoOnly pages with a reading bookmark.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: the result ordering (newest first) and the fact that ordering switches to bookmark time when bookmarked=true. It doesn't mention pagination or result shape, but that is a minor gap against the annotation coverage.

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?

Two compact sentences, front-loaded with the primary behavior, then the conditional mode. No filler or restated title text.

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?

Complete enough for a simple two-param read tool: purpose, both parameter effects, and ordering are all stated, and there is no output schema whose return values would need narrating. Pagination/limit interplay with the default of 20 is left to the schema, which is acceptable.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. However, the description adds meaning the schema lacks: with bookmarked=true the sort key changes to 'newest bookmark first' rather than newest update, which the boolean's own description ('Only pages with a reading bookmark') does not convey.

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 ('Lists the most recently updated pages') with a clear ordering, plus a distinct mode for bookmarked pages. It doesn't explicitly contrast itself with siblings like search or get_page, but the recent-list semantics are clearly separable from them.

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 only implied: the description explains what bookmarked=true does but never says when to reach for this tool versus search or list_tags. An agent can infer the context (browse-by-recency) but there are no explicit conditions or alternatives.

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