Search1API MCP Server

Explore trending topics

trending

Read-only

Fetch currently popular GitHub repositories or Hacker News stories, including titles, URLs, and short descriptions, to answer questions about what is popular now.

Instructions

List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now. Returns each item's title, URL, and a short description when the platform provides one.

Input Schema

Name	Required	Description	Default
`max_results`	No	How many trending items the answer needs, from the top of the list
`search_service`	Yes	Where to look: GitHub for popular open-source repositories, Hacker News for stories developers are discussing	github

Output Schema

Name	Required	Description	Default
`results`	Yes	Trending items reported by the platform

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.9.0Oct 29, 2026

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of trending items to return"New value: +"How many trending items the answer needs, from the top of the list"

changedInput schema / properties / search_service / description

Previous value: -"Platform whose trending items should be returned"New value: +"Where to look: GitHub for popular open-source repositories, Hacker News for stories developers are discussing"

addedOutput schema / properties / results / description

Added value: +"Trending items reported by the platform"

addedOutput schema / properties / results / items / properties / description / description
```
Added value: +"Repository summary or story context, when available"
```
addedOutput schema / properties / results / items / properties / title / description
```
Added value: +"Repository name or story headline"
```
addedOutput schema / properties / results / items / properties / url / description
```
Added value: +"Link to the repository or story"
```

Changed4 schema fields changedv0.4.0Jul 29, 2026

addedInput schema / properties / max_results / maximum
```
Added value: +50
```
addedInput schema / properties / max_results / minimum
```
Added value: +1
```

changedInput schema / properties / search_service / description

Previous value: -"Specify the platform to get trending topics from"New value: +"Platform whose trending items should be returned"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedv0.1.8May 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety and network profile is covered upstream. The description adds genuine value by disclosing the return shape (title, URL, short description when available), but adds nothing on freshness, rate limits, or result ordering beyond 'top of the list'.

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?

Two tight sentences with no filler; the action and scope lead, and the return-shape note follows. Every clause earns its place.

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?

Output schema exists so return values need not be detailed, and annotations cover safety and openness; the description correctly avoids duplicating those. Only small gaps remain around what 'trending' means in terms of time window or ranking.

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 both parameters are fully documented with defaults, bounds, and enum values in the schema itself. The description merely restates the two sources and adds no format or usage nuance beyond it, so baseline 3 applies.

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?

States a specific verb ('List') and resource ('currently trending repositories or stories') plus the two sources, so the agent knows exactly what comes back. It stops short of explicitly contrasting with the sibling 'news' tool, which is the closest potential overlap.

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 a clear triggering condition ('when the user asks what is popular now'), which is more than most definitions offer. It gives no explicit when-not guidance or named alternative for non-trending lookups, leaving that inference to the agent.

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

Deploy Server