Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

list_recent_documents

Retrieve recently modified documents from Outline Wiki to track changes and stay updated on content revisions.

Instructions

Get list of recently modified documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The handler function that implements the core logic: calls Outline API to list recent documents sorted by updatedAt DESC and formats the results.
    async list_recent_documents(args: ListRecentDocumentsInput) {
      const { data } = await apiCall(() =>
        apiClient.post<OutlineDocument[]>('/documents.list', {
          limit: args.limit,
          sort: 'updatedAt',
          direction: 'DESC',
        })
      );
      return formatRecentDocuments(data || [], baseUrl);
    },
  • Zod schema defining the input: optional limit (default 10).
    export const listRecentDocumentsSchema = z.object({ limit: limit.default(10) });
  • src/lib/tools.ts:56-60 (registration)
    Registers the tool in allTools[] with MCP-compatible JSON schema derived from Zod schema.
    createTool(
      'list_recent_documents',
      'Get list of recently modified documents.',
      'list_recent_documents'
    ),
  • Maps tool name to schema in central toolSchemas record used by tool definitions.
    list_recent_documents: listRecentDocumentsSchema,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get list' implies a read-only operation, the description doesn't address important behavioral aspects like what 'recently modified' means (time window criteria), whether results are paginated, what format the list returns, or any rate limits or authentication requirements.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple list operation and front-loads the essential information.

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 no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It doesn't explain what constitutes 'recently modified', what data is returned, or how results are ordered. Given the complexity of document management systems and the lack of structured metadata, more context is needed.

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?

The description mentions no parameters, while the schema has one parameter (limit) with 0% description coverage. Since the description adds no parameter information beyond what's in the schema, and with only one parameter that's reasonably self-explanatory from its name and constraints, a baseline score of 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?

The description 'Get list of recently modified documents' clearly states the verb ('Get list') and resource ('recently modified documents'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar sibling tools like 'list_archived_documents', 'list_collections', or 'search_documents', which prevents a perfect score.

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. With sibling tools like 'search_documents', 'list_archived_documents', and 'list_collections' available, there's no indication of when 'recently modified' filtering is appropriate versus other listing or search approaches.

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