Skip to main content
Glama
Sign In
mcp-archive

mcp-archive

by jeffereychown-Max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_archive_items

Search Internet Archive for books, audio, video, software, and other media by keyword query, with optional media type filter and result count limit.

Instructions

Search Internet Archive items (books, audio, video, software, etc.).

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": {
      "query": "<query>"
    },
    "name": "search_archive_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
mediatypeNotexts
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, and the description only states it searches items. It does not disclose behavior such as pagination, result ordering, or what happens with empty queries.

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 a single concise sentence that is easy to read. However, it is overly terse and could be expanded to include more detail without becoming verbose.

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?

Given no output schema and minimal parameter descriptions, the description does not provide enough context for an agent to understand what the tool returns or how it behaves. Lacks details on pagination, result format, or error handling.

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 hints at media types ('books, audio, video, software') but does not explicitly link to the 'mediatype' parameter or explain 'query' and 'limit'. Some value added, but insufficient.

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

Purpose4/5

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

The description clearly states the tool searches Internet Archive items and lists example media types. However, it does not differentiate from sibling tools like 'get_archived' which might also search items.

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?

No guidance on when to use this tool versus alternatives like 'archive_url' or 'list_snapshots'. No context about prerequisites or limitations.

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

Deploy Server

Other Tools