Skip to main content
Glama

search_wiki_pages

Find Azure DevOps wiki pages by searching titles and content with specific terms to locate project documentation efficiently.

Instructions

Search for wiki pages by title or content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
search_termYesThe term to search for in page titles and content.

Implementation Reference

  • The primary handler function implementing the search_wiki_pages tool. It lists all wiki pages, fetches content for each, and returns matching pages based on search term in path or content.
    def search_wiki_pages(self, project, wiki_identifier, search_term):
        """
        Search for wiki pages by title or content.
        """
        pages = self.list_wiki_pages(project, wiki_identifier)
        matching_pages = []
        
        for page_info in pages:
            try:
                # Get page content to search in
                page = self.wiki_client.get_page(
                    project=project,
                    wiki_identifier=wiki_identifier,
                    path=page_info["path"],
                    include_content=True
                )
                
                # Search in path (title) and content
                if (search_term.lower() in page_info["path"].lower() or 
                    (page.page.content and search_term.lower() in page.page.content.lower())):
                    matching_pages.append({
                        "path": page_info["path"],
                        "url": page_info["url"],
                        "content_preview": page.page.content[:200] + "..." if page.page.content and len(page.page.content) > 200 else page.page.content
                    })
            except Exception:
                # Skip pages that can't be accessed
                continue
                
        return matching_pages
  • The MCP tool registration for search_wiki_pages, including name, description, and input schema definition.
    types.Tool(
        name="search_wiki_pages",
        description="Search for wiki pages by title or content.",
        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."
                },
                "search_term": {
                    "type": "string", 
                    "description": "The term to search for in page titles and content."
                },
            },
            "required": ["project", "wiki_identifier", "search_term"],
            "additionalProperties": False
        }
    ),
  • Dispatch handler in the server that calls the client method for search_wiki_pages.
    elif name == "search_wiki_pages":
        return self.client.search_wiki_pages(**arguments)
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't disclose whether this is a read-only operation, how results are returned (format, pagination), performance characteristics, or authentication requirements. 'Search' implies read-only, but this isn't explicitly stated.

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 wasted words. It's appropriately sized for a search tool and front-loads the core functionality without unnecessary elaboration.

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 search tool with 3 required parameters and no annotations or output schema, the description is insufficient. It doesn't explain what the search returns, how results are structured, whether there are limitations (e.g., partial matches, case sensitivity), or how it differs from other wiki/page retrieval tools in the sibling list.

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 documents all three parameters. The description adds minimal value by mentioning 'title or content' which relates to 'search_term', but doesn't provide additional context about parameter interactions, format expectations, or search behavior beyond what's in the schema.

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 verb ('search') and resource ('wiki pages'), specifying the search scope ('by title or content'). It distinguishes from generic list operations but doesn't explicitly differentiate from sibling tools like 'search_work_items' or 'get_wiki_page_by_title'.

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 on when to use this tool versus alternatives like 'list_wiki_pages', 'get_wiki_page_by_title', or 'search_work_items'. The description implies searching across titles and content but provides no context about prerequisites, limitations, or comparison to other search tools.

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