Skip to main content
Glama
mixophrygian

Browser History Analysis MCP

by mixophrygian

search_browser_history

Search browser history data to find specific URLs and titles matching your query terms for analysis and reporting.

Instructions

Search browser history for specific queries. Use this after getting history data.

Args:
    query: Search term to look for in URLs and titles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server/main.py:82-89 (registration)
    MCP registration of the 'search_browser_history' tool. Provides the tool schema via signature and docstring, acts as a thin wrapper calling the core implementation.
    @mcp.tool()
    async def search_browser_history(query: str) -> List[HistoryEntryDict]:
        """Search browser history for specific queries. Use this after getting history data.
        
        Args:
            query: Search term to look for in URLs and titles
        """
        return await tool_search_browser_history(query, CACHED_HISTORY)
  • Core handler logic: Ensures history is loaded (cached or fetches fresh 7-day history), performs case-insensitive substring matching on entry URLs and titles, returns matching HistoryEntryDict objects.
    async def tool_search_browser_history(query: str, CACHED_HISTORY: CachedHistory) -> List[HistoryEntryDict]:
        if not CACHED_HISTORY.has_history():
            history = await tool_get_browser_history(7, CACHED_HISTORY, "", True)
        else:
            history = CACHED_HISTORY.get_history()
        
        query_lower = query.lower()
        results = []
        
        for entry in history:
            url = entry.get('url', '')
            title = entry.get('title', '')
            
            # Handle None values safely
            if (isinstance(url, str) and query_lower in url.lower()) or \
               (isinstance(title, str) and query_lower in title.lower()):
                results.append(entry)
        
        return results
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions searching 'for specific queries' and using it 'after getting history data', but lacks details on permissions, rate limits, response format, or whether it's read-only or destructive. For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is appropriately sized with two sentences and a parameter explanation. It's front-loaded with the main purpose, and the 'Args' section adds necessary detail without redundancy. However, the phrase 'Use this after getting history data' could be more specific, and overall structure is efficient but not perfectly polished.

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 complexity (simple search with one parameter), an output schema exists, and no annotations are provided, the description is minimally adequate. It covers the basic purpose and parameter semantics but lacks behavioral details and clear differentiation from siblings. With an output schema, it doesn't need to explain return values, but more context on usage and behavior would improve completeness.

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?

The description adds meaning beyond the input schema by explaining that the 'query' parameter is a 'Search term to look for in URLs and titles'. This clarifies the parameter's purpose, but since schema description coverage is 0% and there's only one parameter, the baseline is 4. However, it doesn't provide additional context like format examples or constraints, so it scores slightly lower.

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: 'Search browser history for specific queries.' It specifies the verb ('search') and resource ('browser history'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_browser_history' or 'analyze_browser_history', which might have overlapping functionality.

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 some usage guidance: 'Use this after getting history data.' This implies a prerequisite or sequence, but it doesn't clarify when to use this tool versus alternatives like 'get_browser_history' or 'analyze_browser_history'. No explicit when-not-to-use or alternative recommendations are given.

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/mixophrygian/browser_history_mcp'

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