Skip to main content
Glama

get_wiki_page_by_title

Find Azure DevOps wiki pages using title search instead of exact paths to simplify navigation and locate documentation quickly.

Instructions

Find a wiki page by title instead of exact path - useful for navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
titleYesTitle or partial title of the page to find.

Implementation Reference

  • Core handler function that lists wiki pages, matches the title by extracting from path, fetches and returns the full matching page or None if not found.
    def get_wiki_page_by_title(self, project, wiki_identifier, title):
        """
        Find wiki page by title instead of exact path.
        """
        pages = self.list_wiki_pages(project, wiki_identifier)
        
        for page in pages:
            # Extract title from path (last part after /)
            page_title = page["path"].split("/")[-1].replace("-", " ").replace("_", " ")
            if title.lower() in page_title.lower() or page_title.lower() in title.lower():
                try:
                    full_page = self.get_wiki_page(project, wiki_identifier, page["path"])
                    return full_page
                except Exception:
                    continue
        
        return None
  • Input schema definition for the get_wiki_page_by_title tool, specifying parameters: project, wiki_identifier, title.
    types.Tool(
        name="get_wiki_page_by_title",
        description="Find a wiki page by title instead of exact path - useful for navigation.",
        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."
                },
                "title": {
                    "type": "string", 
                    "description": "Title or partial title of the page to find."
                },
            },
            "required": ["project", "wiki_identifier", "title"],
            "additionalProperties": False
        }
    ),
  • Server-side dispatch and response formatting for the get_wiki_page_by_title tool call, invoking the client method and formatting the output.
    elif name == "get_wiki_page_by_title":
        page = self.client.get_wiki_page_by_title(**arguments)
        if page:
            return {
                "path": page.page.path,
                "url": page.page.url,
                "content": page.page.content,
            }
        else:
            return {"message": f"No page found with title '{arguments['title']}'"}
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the tool is 'useful for navigation', hinting at a read-only, non-destructive operation, but doesn't explicitly state this. It doesn't disclose behavioral traits like whether it returns exact or partial matches, error handling for missing pages, authentication needs, rate limits, or return format. For a lookup tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 extremely concise and front-loaded: two short phrases that directly state the tool's purpose and key differentiator. Every word earns its place, with no redundant information. The structure efficiently communicates the core idea without unnecessary elaboration, making it easy for an agent to parse quickly.

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?

Given the tool's moderate complexity (3 required parameters, no output schema, no annotations), the description is minimally adequate. It clarifies the lookup method (by title vs. path) but lacks details on behavior, output, or differentiation from siblings like 'search_wiki_pages'. Without annotations or output schema, the description should do more to explain what the tool returns or how it handles edge cases, but it meets a basic threshold for a read operation.

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 (project, wiki_identifier, title) with clear descriptions. The description adds no additional parameter semantics beyond implying 'title' can be partial ('Title or partial title' is in the schema). With high schema coverage, the baseline is 3, as the description doesn't compensate with extra details like format examples or constraints.

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 tool's purpose: 'Find a wiki page by title instead of exact path' with the specific verb 'find' and resource 'wiki page'. It distinguishes itself from sibling 'get_wiki_page' (which likely uses exact path) by emphasizing 'by title instead of exact path', though it doesn't explicitly name the sibling. The 'useful for navigation' adds context but doesn't fully differentiate from all title-based alternatives like 'search_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 Guidelines3/5

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

The description provides implied usage guidance: use this tool 'instead of exact path' and 'useful for navigation'. However, it doesn't explicitly state when to use this tool versus alternatives like 'search_wiki_pages' (which might handle partial titles differently) or 'get_wiki_page' (the exact-path sibling). No exclusions or prerequisites are mentioned, leaving some ambiguity about the best choice among title-based lookup 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