Skip to main content
Glama

search_archive

Search Internet Archive collections of uploaded media using Lucene queries to find historical books, lecture recordings, archived films, software releases, and more.

Instructions

Search Internet Archive collections (uploaded books, audio, video, software items) using Lucene query syntax.

This is NOT a search over the Wayback Machine web crawl. It only returns items that someone has uploaded to archive.org as a discrete media item.

Do NOT use this for:

  • Current news, journalism, or recent events

  • Government circulars, press releases, or official web pages

  • Wikipedia articles or any live web content

  • "What was on this website" / "what URLs are archived" — use search_domain or lookup_snapshots for those.

Good uses: historical books, lecture recordings, archived films, software releases, podcast episodes, scanned magazines. Use Lucene fields when possible (e.g. subject:"civil war", creator:"NASA", collection:librivoxaudio).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
mediatypeNo
year_fromNo
year_toNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses it returns only uploaded discrete items, not web pages. Mentions Lucene fields. No annotations provided, so description carries burden; it is mostly transparent, but lacks info on rate limits or authentication.

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

Conciseness5/5

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

Concise, front-loaded, uses bullet points for negative usage and good uses, no wasted words.

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?

Good overview but lacks details on parameter usage, pagination, or output structure. Output schema exists but is not described; parameter details are missing for effective use.

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%. The description does not elaborate on query syntax, mediatype, year_from, year_to, or limit parameters, relying solely on parameter names.

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?

Clearly states it searches Internet Archive collections using Lucene syntax, distinguishes from Wayback Machine search, and lists good uses.

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?

Explicitly lists what NOT to use for (news, government circulars, Wikipedia, web crawl) and suggests alternative tools like search_domain and lookup_snapshots.

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/lakshyamehta03/wayback-machine-mcp'

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