Skip to main content
Glama
Sign In
Outline MCP Server

Outline MCP Server

by bysonte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Buscar documentos de Outline

outline_search_documents

Search across all Outline instance documents using a text query. Optionally limit the number of results to a maximum of 100.

Instructions

Busca documentos en toda la instancia de Outline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "outline_search_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTexto de búsqueda
limitNoNúmero máximo de resultados

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits like idempotency, authentication needs, or that it is a read-only operation. The agent lacks critical safety information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence conveying the core purpose. It is concise but could be slightly more informative without becoming verbose.

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

Completeness3/5

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

With full schema parameter coverage but no output schema or description of return value format, the description lacks completeness. Missing details like response structure (e.g., list of document IDs vs full documents) and pagination behavior.

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 100% with clear parameter descriptions ('search text', 'max results'). The tool description adds no extra parameter meaning, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'search documents across the entire Outline instance', specifying verb (search), resource (documents), and scope (entire instance). This distinguishes it from sibling tools like get_document or list_documents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The verb 'search' implies use when needing to find documents by query. While not explicitly stating when-not or alternatives, it is clear enough for selecting this tool over others.

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

Deploy Server

Other Tools