MCP Webpage Timestamps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_timestampsC | Extract creation, modification, and publication timestamps from a webpage |
| batch_extract_timestampsB | Extract timestamps from multiple webpages in batch |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have overlapping purposes with unclear boundaries. 'extract_timestamps' handles a single webpage, while 'batch_extract_timestamps' handles multiple webpages, but both essentially perform the same core timestamp extraction function. An agent might struggle to choose between them when processing a single webpage, as the batch tool could theoretically handle that case too.
The naming follows a perfectly consistent pattern with clear verb_noun structure. Both tools use 'extract_timestamps' as the base noun phrase, with 'batch_' as a descriptive prefix for the multi-page version. There are no deviations in style or convention.
With only 2 tools, this server feels severely under-scoped for timestamp extraction from webpages. A more complete surface would likely include tools for validating timestamps, formatting them, or handling different timestamp types. The minimal tool count suggests incomplete coverage of the domain.
The toolset is severely incomplete for webpage timestamp extraction. While it covers extraction from single and multiple pages, there are obvious gaps: no tools for timestamp validation, conversion between formats, filtering by date ranges, or handling edge cases like missing timestamps. This limited surface will likely cause agent failures in real-world scenarios.