Skip to main content
Glama

get_document_id_from_title

Find a document's ID using its title, even with partial matches. Useful for referencing or verifying documents in MCP Outline Server operations.

Instructions

    Locates a document ID by searching for its title.
    
    IMPORTANT: This tool first checks for exact title matches 
    (case-insensitive). If none are found, it returns the best partial 
    match instead. This is useful when you're not sure of the exact title 
    but need 
    to reference a document in other operations. Results are more accurate 
    when you provide more of the actual title in your query.
    
    Use this tool when you need to:
    - Find a document's ID when you only know its title
    - Get the document ID for use in other operations
    - Verify if a document with a specific title exists
    - Find the best matching document if exact title is unknown
    
    Args:
        query: Title to search for (can be exact or partial)
        collection_id: Optional collection to limit the search to
        
    Returns:
        Document ID if found, or best match information
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idNo
queryYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining the search behavior (exact case-insensitive match first, then partial match), accuracy considerations, and return format. It doesn't mention rate limits, authentication needs, or error conditions, but provides substantial operational context.

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 clear sections (purpose, important behavior, usage guidelines, args, returns) but slightly verbose in the usage guidelines section. Every sentence adds value, and key information is front-loaded with the core purpose stated first.

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?

For a 2-parameter tool with no annotations and no output schema, the description provides comprehensive context about behavior, parameters, and usage. It explains the return value format ('Document ID if found, or best match information'), though could be more specific about the 'best match information' structure.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'query' is described as 'Title to search for (can be exact or partial)' and 'collection_id' as 'Optional collection to limit the search to'. This adds crucial meaning beyond the bare schema.

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 the tool's purpose with specific verbs ('locates', 'searching') and resource ('document ID by title'), distinguishing it from siblings like search_documents or read_document. It explicitly differentiates by focusing on ID retrieval rather than document content or broader search.

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?

The description provides explicit usage scenarios in a bulleted list, including when to use it ('when you only know its title', 'for use in other operations') and when it's appropriate ('if exact title is unknown'). It distinguishes from alternatives by emphasizing ID retrieval rather than document access.

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

Related 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