Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

list_document_comments

Retrieve comments on a specific Outline wiki document to review feedback and discussions.

Instructions

Get list of comments on a document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYes
limitNo
offsetNo

Implementation Reference

  • The handler function that executes the list_document_comments tool. It calls the Outline API endpoint '/comments.list' with documentId, limit, and offset parameters, then formats the returned comments using formatComments.
    async list_document_comments(args: ListDocumentCommentsInput) {
      const { data } = await apiCall(() =>
        apiClient.post<OutlineComment[]>('/comments.list', {
          documentId: args.documentId,
          limit: args.limit,
          offset: args.offset,
        })
      );
      return formatComments(data || []);
    },
  • Zod schema for ListDocumentCommentsInput, defining required documentId, optional limit (default 25, max 100), and offset (default 0).
    export const listDocumentCommentsSchema = z.object({
      documentId,
      limit: limit.default(25),
      offset,
    });
  • Tool registration in the allTools array using createTool, which converts the Zod schema to JSON schema and sets the tool name and description for MCP protocol.
    createTool(
      'list_document_comments',
      'Get list of comments on a document.',
      'list_document_comments'
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation ('Get list'), but doesn't disclose pagination behavior (limit/offset), authentication needs, rate limits, error conditions, or what the returned list structure looks like. For a tool with 3 parameters and no output schema, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately front-loaded with the core purpose, making it easy to scan and understand quickly without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no annotations, no output schema), the description is insufficiently complete. It doesn't explain parameter usage, return format, error handling, or how it relates to sibling tools. For a list operation with pagination parameters, more context is needed to use it effectively beyond just knowing it fetches comments.

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?

Schema description coverage is 0%, so the description must compensate but fails to do so. It mentions 'documentId' implicitly via 'on a document', but doesn't explain what format this ID should be, where to get it, or the purpose of 'limit' and 'offset' parameters. The description adds almost no meaning beyond the bare schema, leaving parameters largely unexplained.

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 clearly states the verb ('Get list') and resource ('comments on a document'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_comment' (singular) or 'get_document' (which might include comments), but the focus on listing comments is specific enough for basic understanding.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention whether this should be used instead of 'get_document' (which might include comments) or 'get_comment' (for a single comment), nor does it specify prerequisites like needing document access. The description only states what it does, not when to choose it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/huiseo/outline-smart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server