Skip to main content
Glama
superagents-lab

Search1API MCP Server

by superagents-lab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Explore trending topics

trending
Read-only

Discover currently trending repositories on GitHub or top stories on Hacker News. Select the platform and set a limit to retrieve popular items.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMaximum number of trending items to return
search_serviceYesPlatform whose trending items should be returnedgithub

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

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

  1. Changed4 schema fields changedv0.4.0
    • 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"
+}
  2. First observedv0.1.8

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint and destructiveHint. The description adds that it lists items from two specific platforms, which is useful context. No contradictions; it supplements annotations well.

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 a single sentence that front-loads the action and scope. Every word is necessary and conveys the purpose efficiently.

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?

The tool has an output schema, so return values need not be described. The description covers the use case and parameters. Minor gap: no mention of potential rate limits or behavior differences between platforms, but overall complete for a simple tool.

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 coverage is 100% with clear parameter descriptions. The description adds no additional parameter-level detail beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the verb 'list' and the resource 'trending repositories or stories' from specific sources (GitHub, Hacker News). It distinguishes from sibling tools like 'search' and 'news' by focusing on 'popular now' trends.

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 explicitly says 'when the user asks what is popular now', providing a clear trigger. It does not specify when not to use or explicitly name alternatives, but the context of sibling tools makes the guidance adequate.

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/superagents-lab/search1api-mcp'

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