Search1API MCP Server

Explore trending topics

trending

Read-only

List popular repositories or stories from GitHub or Hacker News when users ask what is popular now.

Instructions

List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`max_results`	No	Maximum number of trending items to return
`search_service`	Yes	Platform whose trending items should be returned	github

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and reach profile is fully covered structurally. The description adds the scope 'currently trending' but nothing about rate limits, auth, or freshness/pagination behavior beyond what the annotations supply.

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?

A single sentence that front-loads the action and payload, then appends the usage trigger. Nothing is wasted, though it is slightly dense and could separate the 'what' from the 'when' more cleanly.

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?

With an output schema present, rich annotations, and full schema description coverage, the description only needs to establish purpose and invocation context, which it does. The one unmentioned detail, that github is the default service, is already carried by the schema.

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 search_service and max_results are already documented in the schema, and the description's mention of GitHub/Hacker News merely echoes the enum. It adds no format, default, or range guidance, so the 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) with the source platforms named, so an agent knows exactly what comes back. It does not explicitly distinguish itself from the sibling 'news' or 'search' tools, which is the only thing keeping it out of the top band.

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 clause 'when the user asks what is popular now' gives clear triggering context and is embedded directly in the description rather than left implicit. There is no exclusion or named alternative, but the invocation condition is unambiguous.

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

Deploy Server