Skip to main content
Glama

list_recently_updated_documents

Read-onlyIdempotent

Retrieve Outline documents ordered by most recent change. Filter by date, collection, or status to see what was updated recently.

Instructions

        Lists documents ordered by most recent change (newest first).

        Answers questions like "what changed this week" without needing
        search keywords. Backed by Outline's search endpoint with an empty
        query, sorted by last-modified time.

        IMPORTANT: date_filter is a coarse server-side window on each
        document's last-modified time. It accepts only "day", "week",
        "month", or "year" (no arbitrary timestamps) and defaults to
        "week". Results are ordered newest-changed first.

        STATUS FILTER: By default this lists published documents only.
        Pass status_filter to include other states. Allowed values are
        "draft", "archived", and "published". Drafts only ever include
        those you are allowed to see.

        PAGINATION: Returns up to limit documents (default 25). Use offset
        to page through older changes.

        Use this tool when you need to:
        - Answer "what documents changed recently / this week"
        - Review recent activity, optionally within one collection
        - Catch up on edits since you last looked

        Args:
            date_filter: Time window on last-modified time. One of "day",
                "week", "month", "year". Defaults to "week".
            collection_id: Optional collection to limit results to
            status_filter: Optional list of statuses to include. Allowed
                values are "draft", "archived", and "published". Defaults
                to published only.
            limit: Maximum number of documents to return (default: 25)
            offset: Number of documents to skip for pagination (default: 0)

        Returns:
            Formatted string listing documents with their IDs and
            last-updated timestamps, newest first
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_filterNoweek
collection_idNo
status_filterNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is conveyed. Description adds behavioral quirks: date_filter restrictions, status filter defaults, pagination details. No contradictions.

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?

Well-structured with sections (IMPORTANT, STATUS FILTER, PAGINATION, use cases). No fluff, but slightly verbose (200 words). Could be trimmed slightly.

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

Completeness4/5

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

Given the simple list functionality and presence of an output schema (not shown but indicated), the description covers all key aspects: behavior, parameters, return format, use cases. Adequate for a non-complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description carries full burden. It explains date_filter enum, collection_id optionality, status_filter values, limit/offset defaults. Good but could add more detail on return format beyond the short note.

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?

Clearly states 'Lists documents ordered by most recent change (newest first).' Distinguishes from siblings like search_documents (keyword-based) and list_archived_documents.

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

Usage Guidelines5/5

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

Explicitly lists use cases: 'Answer what documents changed recently / this week', 'Review recent activity', 'Catch up on edits'. Implicitly excludes keyword search scenarios.

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/Vortiago/mcp-outline'

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