SiteGraph

url_timeline

Retrieve a URL's archive timeline: first and last captures, declared publish dates from live and earliest archived copies, and removal status to verify when content appeared or vanished.

Instructions

First/latest archive capture, declared publish dates (live + earliest archived copy), removal status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "url_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

C2.6/5.0

Behavior3/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. It does disclose the data categories returned (first/latest capture, declared live and earliest-archived publish dates, removal status), which is meaningful behavioral scope, but it says nothing about whether the lookup is read-only, its cost, failure modes, or what happens for uncaptured URLs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no wasted words, but the fragmentary telegraphic style is under-specified rather than concise. There is no leading verb to anchor the reader, so the key information is not properly front-loaded.

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

Completeness2/5

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

An output schema exists, so return-value detail is not required, but the description still omits everything an agent needs to decide when this tool applies and how to prepare the URL. For a tool surrounded by four related timeline/provenance siblings, that omission is significant.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter 'url' has no description anywhere. The description does not clarify whether the URL should be normalized, include scheme, or point to the live page versus an archived snapshot, so it fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase fragment rather than a verb+resource statement, but it does convey that the tool produces a timeline for a URL covering archive captures, publish dates, and removal status. It never states the operation (retrieve/compute) and gives no differentiation from siblings like claim_timeline, so the purpose is only inferable.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus claim_timeline, fact_checks, image_provenance, or claimreview_from_url. Nothing indicates prerequisites, such as whether the URL must be live or archived, or what to do when no captures exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server