Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

batch_move_documents

Move multiple Outline wiki documents simultaneously to reorganize content efficiently. Specify document IDs and target collection or parent document.

Instructions

Move multiple documents at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdsYes
collectionIdNo
parentDocumentIdNo

Implementation Reference

  • The core handler function for the batch_move_documents tool. It performs access check, then batches API calls to move each document to the specified collection or parent using the Outline /documents.move endpoint.
    async batch_move_documents(args: BatchMoveDocumentsInput) {
      checkAccess(config, 'batch_move_documents');
    
      return runBatch(args.documentIds, async (documentId) => {
        try {
          const payload: Record<string, unknown> = { id: documentId };
          if (args.collectionId) payload.collectionId = args.collectionId;
          if (args.parentDocumentId !== undefined) payload.parentDocumentId = args.parentDocumentId;
    
          const { data } = await apiCall(() =>
            apiClient.post<OutlineDocument>('/documents.move', payload)
          );
          return { success: true, id: data.id, title: data.title };
        } catch (error) {
          return { success: false, documentId, error: getErrorMessage(error) };
        }
      });
    },
  • Zod input schema definition for batch_move_documents tool, validating documentIds array and optional collectionId/parentDocumentId.
    export const batchMoveDocumentsSchema = z.object({
      documentIds,
      collectionId: collectionId.optional(),
      parentDocumentId: z.string().uuid().nullable().optional(),
    });
  • Registers the batch_move_documents tool in the allTools array by creating a ToolDefinition from its Zod schema.
    createTool(
      'batch_move_documents',
      'Move multiple documents at once.',
      'batch_move_documents'
    ),
  • Maps the batchMoveDocumentsSchema to the 'batch_move_documents' tool name in the central toolSchemas record.
    batch_move_documents: batchMoveDocumentsSchema,
  • The createBatchHandlers factory function that produces the handler object including batch_move_documents.
    }
    
    export function createBatchHandlers({ apiClient, apiCall, config }: AppContext) {
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 ('move') without disclosing behavioral traits. It doesn't mention permissions required, whether moves are reversible, effects on document metadata or links, error handling for invalid IDs, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 zero waste—'Move multiple documents at once' is front-loaded and appropriately sized for the tool's purpose, making it easy to parse 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?

Given the tool's complexity (batch mutation with 3 parameters), no annotations, no output schema, and 0% schema coverage, the description is incomplete. It lacks details on behavior, parameters, usage context, and expected outcomes, which are critical for safe and effective tool invocation by an AI agent.

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 doesn't explain what 'documentIds', 'collectionId', or 'parentDocumentId' represent, their formats (e.g., UUIDs), or how they interact (e.g., moving documents to a collection or under a parent). This leaves key semantics undocumented.

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 'Move multiple documents at once' clearly states the verb ('move') and resource ('documents'), with the 'multiple...at once' specifying batch operation. However, it doesn't explicitly differentiate from the sibling 'move_document' tool, which handles single document moves, though the batch nature is implied.

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 'move_document' for single moves or other batch operations. The description implies batch usage but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer context from tool names alone.

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