Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

batch_archive_documents

Archive multiple documents simultaneously in Outline Wiki to organize your workspace by removing outdated or completed files in bulk.

Instructions

Archive multiple documents at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdsYes

Implementation Reference

  • The main handler function for the 'batch_archive_documents' tool. It checks access, then uses runBatch to archive each document ID via the Outline API's /documents.archive endpoint, collecting success/failure results.
    async batch_archive_documents(args: BatchArchiveDocumentsInput) {
      checkAccess(config, 'batch_archive_documents');
    
      return runBatch(args.documentIds, async (documentId) => {
        try {
          const { data } = await apiCall(() =>
            apiClient.post<OutlineDocument>('/documents.archive', { id: documentId })
          );
          return { success: true, id: data.id, title: data.title };
        } catch (error) {
          return { success: false, documentId, error: getErrorMessage(error) };
        }
      });
    },
  • Zod schema definition for the tool input: requires an array of documentIds.
    export const batchArchiveDocumentsSchema = z.object({ documentIds });
  • TypeScript type inferred from the batchArchiveDocumentsSchema for use in handlers.
    export type BatchArchiveDocumentsInput = z.infer<typeof batchArchiveDocumentsSchema>;
  • Registration of the tool in the allTools array using createTool, which converts the Zod schema to JSON schema for MCP.
    createTool(
      'batch_archive_documents',
      'Archive multiple documents at once.',
      'batch_archive_documents'
    ),
  • The tool schema is mapped in toolSchemas object, used by createTool in tools.ts.
    batch_archive_documents: batchArchiveDocumentsSchema,
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose permissions needed, whether archiving is reversible (though 'unarchive_document' exists), rate limits, or what happens to archived documents (e.g., moved to a list accessible via 'list_archived_documents').

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly.

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 mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, and outcomes, failing to compensate for the missing structured data, which could lead to incorrect usage by an agent.

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?

Schema description coverage is 0%, so the description must compensate but adds no parameter details. It implies 'documentIds' are needed but doesn't explain format, sourcing, or constraints. With 1 parameter and no schema descriptions, baseline is 3 as the description doesn't add meaningful semantics beyond the obvious.

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 ('archive') and resource ('multiple documents'), making the purpose understandable. It distinguishes from 'archive_document' by specifying batch operation, though it doesn't explicitly contrast with 'batch_delete_documents' or 'batch_move_documents' which are similar batch operations on documents.

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 like 'archive_document' (for single documents) or 'batch_delete_documents' (for deletion instead of archiving). The description implies batch usage but lacks explicit context or exclusions.

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