Skip to main content
Glama

get_recent_wiki_pages

Retrieve recently modified wiki pages from Azure DevOps projects to track documentation updates and team activity.

Instructions

Get recently modified wiki pages based on activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
limitNoMaximum number of pages to return (default: 10).

Implementation Reference

  • The primary handler function that implements the tool logic: retrieves all wiki pages, annotates with latest view activity as a proxy for recency, sorts descending by activity date, and returns the top 'limit' pages.
    def get_recent_wiki_pages(self, project, wiki_identifier, limit=10):
        """
        Get recently modified wiki pages.
        """
        pages = self.list_wiki_pages(project, wiki_identifier)
        
        # Sort by view stats if available (proxy for recent activity)
        pages_with_activity = []
        for page in pages:
            if page.get("view_stats"):
                latest_activity = max(page["view_stats"], key=lambda x: x["date"]) if page["view_stats"] else None
                pages_with_activity.append({
                    **page,
                    "latest_activity": latest_activity
                })
            else:
                pages_with_activity.append({
                    **page,
                    "latest_activity": None
                })
        
        # Sort by latest activity date
        pages_with_activity.sort(
            key=lambda x: x["latest_activity"]["date"] if x["latest_activity"] else "1900-01-01",
            reverse=True
        )
        
        return pages_with_activity[:limit]
  • Input schema defining parameters: project (required string), wiki_identifier (required string), limit (optional integer, default 10).
    inputSchema={
        "type": "object",
        "properties": {
            "project": {
                "type": "string", 
                "description": "The name or ID of the project."
            },
            "wiki_identifier": {
                "type": "string", 
                "description": "The name or ID of the wiki."
            },
            "limit": {
                "type": "integer", 
                "description": "Maximum number of pages to return (default: 10)."
            },
        },
        "required": ["project", "wiki_identifier"],
        "additionalProperties": False
    }
  • Tool registration in the self.tools list, including name, description, and schema. Exposed via list_tools() handler.
        name="get_recent_wiki_pages",
        description="Get recently modified wiki pages based on activity.",
        inputSchema={
            "type": "object",
            "properties": {
                "project": {
                    "type": "string", 
                    "description": "The name or ID of the project."
                },
                "wiki_identifier": {
                    "type": "string", 
                    "description": "The name or ID of the wiki."
                },
                "limit": {
                    "type": "integer", 
                    "description": "Maximum number of pages to return (default: 10)."
                },
            },
            "required": ["project", "wiki_identifier"],
            "additionalProperties": False
        }
    ),
  • Dispatch handler in call_tool that proxies arguments to the client method.
    elif name == "get_recent_wiki_pages":
        return self.client.get_recent_wiki_pages(**arguments)
  • Helper method called by get_recent_wiki_pages to fetch wiki pages with view_stats used for sorting recency.
    def list_wiki_pages(self, project, wiki_identifier):
        pages_batch_request = WikiPagesBatchRequest(
            top=100  # Retrieve up to 100 pages
        )
        pages = self.wiki_client.get_pages_batch(
            project=project,
            wiki_identifier=wiki_identifier,
            pages_batch_request=pages_batch_request
        )
        return [
            {
                "path": page.path,
                "url": getattr(page, 'url', ''),  # Handle missing url attribute
                "view_stats": [
                    {"date": stat.date.isoformat(), "count": stat.count}
                    for stat in page.view_stats
                ] if page.view_stats else []
            }
            for page in pages
        ]
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, the description doesn't address important behavioral aspects like whether this requires authentication, what format the results return, whether there's pagination, rate limits, or error conditions. The phrase 'based on activity' is vague about what activity metrics determine 'recently modified'.

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 unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information ('Get recently modified wiki pages').

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?

For a read-only tool with full parameter documentation in the schema, the description is minimally adequate but has significant gaps. Without annotations or output schema, the description should ideally provide more behavioral context about what 'recently modified' means, the return format, and how this differs from similar sibling tools. The current description is incomplete for optimal agent understanding.

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%, so the schema already fully documents all three parameters (project, wiki_identifier, limit). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters or provide usage examples. This meets the baseline for high schema coverage.

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 ('Get recently modified wiki pages') and resource ('wiki pages'), with the qualifier 'based on activity' providing useful context about the selection criteria. However, it doesn't explicitly differentiate this tool from sibling tools like 'list_wiki_pages' or 'search_wiki_pages' which might also retrieve wiki pages.

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 about when to use this tool versus alternatives. With multiple sibling tools that retrieve wiki pages (list_wiki_pages, search_wiki_pages, get_wiki_page, get_wiki_page_by_title), there's no indication of when this 'recently modified' retrieval is preferred over other listing or searching 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/xrmghost/mcp-azure-devops'

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