Skip to main content
Glama
RobinBially

search-rotation

by RobinBially
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Web Search

web_search

Get reliable web search results by rotating across multiple free APIs with automatic failover, including numbered titles, URLs, and snippets.

Instructions

Web search with automatic round-robin across multiple free search APIs (Tavily, Firecrawl, Parallel, Exa, Google PSE, DuckDuckGo) including transparent failover. Returns numbered results with title, URL, snippet and publication date when available. Time filters restrict rotation and failover to compatible providers; never silently dropped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
engineNoPreferred engine id; failover to the other engines stays active
endDateNoEnd date YYYY-MM-DD (through this date, subject to provider boundary semantics). Cannot combine with timeRange.
startDateNoStart date YYYY-MM-DD. May be used alone or with endDate; cannot combine with timeRange.
timeRangeNoRelative UTC date window: day=1, week=7, month=30, year=365 days through today. Cannot combine with startDate/endDate; day precision, not rolling hours.
numResultsNoOptional result count (1–20). Omit to use the dashboard setting: a custom count or the provider default.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.4.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / endDate / $ref
      Removed value: -"#/properties/startDate"
    • addedInput schema / properties / endDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / endDate / type
      Added value: +"string"
  2. Changed3 schema fields changedv0.4.2
    • addedInput schema / properties / endDate
      Added value: +{
+  "$ref": "#/properties/startDate",
+  "description": "End date YYYY-MM-DD (through this date, subject to provider boundary semantics). Cannot combine with timeRange."
+}
    • addedInput schema / properties / startDate
      Added value: +{
+  "description": "Start date YYYY-MM-DD. May be used alone or with endDate; cannot combine with timeRange.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / timeRange
      Added value: +{
+  "description": "Relative UTC date window: day=1, week=7, month=30, year=365 days through today. Cannot combine with startDate/endDate; day precision, not rolling hours.",
+  "enum": [
+    "day",
+    "week",
+    "month",
+    "year"
+  ],
+  "type": "string"
+}
  3. First observedv0.3.3

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full transparency burden. It discloses significant behavioral traits: automatic round-robin across providers, transparent failover, and the guarantee that time filters are never silently dropped. It also specifies the result shape, which is especially valuable because no output schema exists.

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?

The description is compact and front-loaded, using only two sentences. It conveys core behavior, provider list, failover semantics, returned fields, and the time-filter guarantee without filler or repetition.

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

Completeness4/5

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

Given six parameters and no output schema, the description covers the essential result format and important behavioral constraints. It does not discuss error handling beyond failover, rate limits, or provider-specific edge cases, so it is thorough but not exhaustive.

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

Parameters4/5

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

The input schema already describes all six parameters with 100% coverage, so the baseline is 3. The description adds extra semantic value by explaining that time filters restrict rotation and failover to compatible providers, a nuance not present in the schema. This justifies a score above baseline.

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?

The description opens with a specific action and resource: web search performed through multiple named APIs. It clearly differentiates this tool from siblings like fetch_url and engine_status by emphasizing search results, round-robin rotation, and failover.

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?

The description provides clear context for when the tool is appropriate: general web searching with automatic provider rotation and date filtering. It does not explicitly state when to prefer fetch_url or engine_status, so it falls short of a perfect 5, but the use case is evident.

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/RobinBially/search-rotation'

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