Skip to main content
Glama

search_ddb

Search German newspaper pages in the Deutsches Zeitungsportal with Solr query syntax, date/place/title filters, and highlighted snippets.

Instructions

Search German newspaper pages in the Deutsches Zeitungsportal.

Covers ~33.8M digitised pages, densest between 1850 and 1949. Results are individual newspaper pages, and each carries highlighted snippets showing where the query matched, with matched terms in {braces} - so a single search is usually enough to judge a hit without downloading anything.

Args: query: Solr query over page OCR text. Supports: - Exact phrases: '"Bert Reese"' - Boolean operators: 'Hellseher AND Telepathie', 'A OR B', 'A NOT B' - Wildcards: 'Hellseh*' - Fuzziness for OCR damage: 'Hanussen~1' - Proximity: '"Hellseher Hanussen"~10' page: Result page number, 1-indexed rows: Results per page (max 100) from_year: Earliest publication year, inclusive to_year: Latest publication year, inclusive paper_title: Restrict to one newspaper title place: Restrict to a place of distribution language: Language code, ISO 639-2 (e.g. 'ger')

Returns: total_results (a true count, not a ranking depth), total_pages, and the matching pages with their metadata, viewer URL and snippets. Results are ordered by relevance; DDB cannot order by date, so chronological work means bounding the query with from_year/to_year and sweeping it whole.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
rowsNo
placeNo
queryYes
to_yearNo
languageNo
from_yearNo
paper_titleNo
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses ordering limitation (cannot sort by date), snippet format (matched terms in braces), and result semantics (total_results as true count). Clearly describes behavioral traits beyond schema.

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?

Well-structured with a clear introductory sentence followed by coverage, result format, and parameter details. Slightly verbose but front-loaded with key information. Every section adds value.

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 tool's complexity (8 parameters, no output schema), the description is remarkably complete. Covers purpose, coverage, result format, behavioral quirks, and detailed parameter usage. No significant gaps.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides extensive parameter details in the Args list, including query syntax (phrases, booleans, wildcards, fuzziness, proximity), and explanations for each field. Fully compensates for missing schema descriptions.

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 the tool searches German newspaper pages in the Deutsches Zeitungsportal. Specifies the resource and action, and implies differentiation from siblings by noting that results include snippets.

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

Usage Guidelines4/5

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

Provides context on coverage (33.8M pages, densest 1850-1949), result format (pages with snippets), and ordering (relevance only). Offers guidance for chronological work but no explicit when-not-to-use or alternatives.

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/nestordemeure/ddb-mcp'

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