Skip to main content
Glama

List your private pages

list_pages

List the miinideck pages the signed-in user has published — each with its private link and current status: when it expires (or 'never expires'), whether it's searchable by search engines, and whether it's password-protected. Also lists pages other people SHARED with the user as a collaborator — those can only have their content replaced (update_page with html, or prepare_upload with page); every other change stays with their owner. Call this to find a page's URL/slug (and see its state) before update_page, delete_page, get_page, or restore_page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, so the description carries the full load; it discloses useful traits: the returned state fields (expiry or 'never expires', search-engine visibility, password protection) and the restricted permissions on collaborator pages. It omits ordering, pagination, and whether listing is subject to rate limits or account scoping, which matter for a list tool with no output schema.

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?

Front-loaded with purpose and scope, and every clause is load-bearing. The middle sentence about collaborator permissions is long and packed, but it conveys a non-obvious constraint rather than 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 enumerates the salient return fields and explains the collaborator inclusion rule, which is enough to call it correctly. A brief note on result ordering or pagination would close the remaining gap for a list operation.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly adds no parameter detail and instead spends its words on scope and return contents.

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?

Specific verb and resource ('List the ... pages'), with explicit scope: the signed-in user's published pages plus pages shared with them as a collaborator. It also names the sibling tools (update_page, delete_page, get_page, restore_page) whose workflow it feeds, so an agent can place it without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Call this to find a page's URL/slug (and see its state) before update_page, delete_page, get_page, or restore_page.' It also states a constraint on collaborator-shared pages — only content replacement via update_page with `html` or prepare_upload with `page` is permitted, everything else stays with the owner — which tells the agent when downstream mutations will fail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources