internet-archive-mcp-server

Get Internet Archive Item

ia_get_item

Read-onlyIdempotent

Retrieve metadata and the file manifest for an Internet Archive item by identifier. Returns title, creator, description, subjects, collections, license, language, the total file count, and a page of files, each with its format, size, and direct download URL. Pages hold up to max_files files (default 50, at most 500 per call) starting at file_offset; set format to keep a single file type (e.g. "DjVuTXT", "Text PDF", "VBR MP3"). The primary tool to act on a search result from ia_search_items. Use ia_get_text to retrieve the readable text of a text item.

Input Schema

Name	Required	Description
`format`	No	Keep only files whose format equals this value, ignoring case — e.g. "DjVuTXT", "Text PDF", "VBR MP3". Applied before paging. Omit to list every format.
`max_files`	No	Maximum number of files to return (default 50). One call returns at most 500: a larger value (up to 300,000) is served as 500, with a notice naming the next file_offset.
`identifier`	Yes	Internet Archive item identifier, e.g. "prideprejudice00aust" (Pride and Prejudice). Obtain from ia_search_items results.
`file_offset`	No	Zero-based position in the (format-filtered) file list to start from (default 0). To read the next page, add the number of files returned to the previous file_offset, or pass the file_offset the notice names.

Output Schema

Name	Required	Description
`cap`	No	The page size applied: max_files, or 500 when a larger value was capped.
`date`	No	Publication or upload date when provided.
`error`	No	Present when the call failed. Absent on success.
`files`	No	This page of the manifest in upstream order — up to max_files files (at most 500) from file_offset, after the format filter.
`shown`	No	Number of files returned on this page.
`title`	No	Item title when provided by the metadata.
`notice`	No	Paging guidance with the next file_offset, or the formats present when the filter matched nothing.
`rights`	No	Rights statement when provided.
`creator`	No	Creator or author name(s) when provided.
`subject`	No	Subject or topic tag(s) when provided.
`language`	No	Language(s) of the item when provided.
`mediatype`	No	Media type (texts, audio, movies, etc.).
`truncated`	No	True when more files remain past this page.
`collection`	No	Collection(s) this item belongs to when provided.
`file_count`	No	Total number of files in the full item manifest, before filtering and paging.
`identifier`	No	The item identifier.
`licenseurl`	No	License URL when provided.
`totalCount`	No	Number of files matching the format filter, before paging.
`description`	No	Item description when provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover read-only, idempotent, and open-world traits, but the description adds substantive behavioral detail beyond them: the default and hard cap on files per page, the notice returned when max_files exceeds the cap, that format filtering occurs before paging, and the zero-based offset model. This is rich operational context for a paged retrieval tool.

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 front-loaded with purpose and then layers on return summary and usage guidance in a logical order. It is efficient and readable, though the long enumeration of returned metadata fields is somewhat redundant given the output schema and could be trimmed.

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 output schema, complete annotations, and 100% parameter coverage, the description supplies everything else an agent needs: scope, return shape summary, pagination limits, format filtering, and sibling alternatives. Nothing material is missing.

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?

Schema description coverage is 100%, so the schema already fully documents identifier, format, max_files, and file_offset. The description restates the paging and filtering behavior but adds no syntax or constraints not already present in the schema, so the baseline of 3 applies.

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?

States a specific verb and resource: retrieve metadata and the file manifest for an Internet Archive item by identifier. It enumerates the returned metadata fields and makes clear it is distinct from ia_get_text, so the agent can identify it immediately.

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 names the upstream context ('primary tool to act on a search result from ia_search_items') and the alternative for text retrieval (ia_get_text). It also explains when to use the format filter and pagination, leaving little to inference.

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

All internet-archive-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.