Skip to main content
Glama
adrianba

edge-history-mcp

by adrianba
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_history

Fetch browsing history entries from a Microsoft Edge profile for a specific day, with visit times, URLs, titles, and transition types.

Instructions

Get Edge browsing history for a profile on a specific day.

Args:
    profile: Profile friendly name (from ``list_profiles``) or directory id.
    date: Day to fetch, formatted ``YYYY-MM-DD``. Day boundaries are
        interpreted in the local machine timezone.
    limit: Maximum number of entries to return (default 10000, capped at
        50000). Non-positive values fall back to the default.

Returns:
    One entry per page visit, ordered by visit time ascending. Each entry
    includes the local ISO ``visit_time``, ``url``, ``title``,
    ``visit_count``, ``typed_count``, ``transition`` type, and the
    ``url_id``/``visit_id`` identifiers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileYes
dateYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: date boundaries in local timezone, default limit of 10000 capped at 50000, return order ascending, and the exact fields returned. This provides complete transparency.

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 well-organized with Args and Returns sections, but it is slightly verbose (e.g., repeating 'profile' explanation). However, every sentence adds value, and the structure aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no annotations, output schema present), the description covers all necessary aspects: parameter semantics, behavioral details, and return structure. It is fully sufficient for an agent to invoke correctly.

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?

Schema coverage is 0%, but the description adds full meaning: profile is friendly name or directory id from list_profiles, date format with timezone interpretation, and limit defaults with cap. This compensates completely for the lack of schema descriptions.

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 starts with 'Get Edge browsing history for a profile on a specific day,' clearly stating the verb and resource. It differentiates from the sibling tool list_profiles by focusing on history retrieval rather than profile listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description explains when to use the tool (fetch history for a profile on a day) and provides argument details like profile source and date format. However, it does not explicitly state when not to use it or mention alternatives beyond the implicit sibling.

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/adrianba/edge-browser-mcp'

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