Skip to main content
Glama
huiseo
by huiseo

list_document_comments

Retrieve comments on a specific Outline wiki document to review feedback, discussions, or annotations. Specify the document ID to access the comment list.

Instructions

Get list of comments on a document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYes
limitNo
offsetNo

Implementation Reference

  • The main handler function that lists comments for a document by calling the Outline API '/comments.list' endpoint with documentId, limit, and offset, then formats the results 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 defining the input parameters for the list_document_comments tool: documentId (required), limit (default 25), offset (default 0).
    export const listDocumentCommentsSchema = z.object({
      documentId,
      limit: limit.default(25),
      offset,
    });
  • Tool registration in the allTools array, creating the MCP tool definition from the schema with name 'list_document_comments' and description.
    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 reveals minimal behavioral information. It implies a read operation ('Get list') but doesn't disclose pagination behavior (limit/offset), rate limits, authentication requirements, error conditions, or what happens with invalid document IDs. The description is functionally accurate but lacks operational context.

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, focused sentence with zero wasted words. It's front-loaded with the core purpose and uses straightforward language. Every word earns its place, making it immediately scannable and understandable.

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?

For a tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain the pagination system (limit/offset), return format, error handling, or relationship to other comment/document operations. The agent would need to guess about important operational aspects.

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 adds no parameter information. It mentions 'document' which maps to 'documentId', but doesn't explain what format this ID should be, where to find it, or that limit/offset parameters exist for pagination control. The description fails to provide meaningful semantic context beyond what's inferable from the tool name.

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 action ('Get list') and resource ('comments on a document'), making the purpose immediately understandable. It distinguishes from siblings like 'get_comment' (singular) and 'add_comment', but doesn't explicitly differentiate from other list tools like 'list_collections' or 'list_recent_documents' beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'get_comment' for a single comment, or how it relates to document viewing workflows. There's no context about prerequisites, permissions, or typical use cases.

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-wiki-mcp'

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