awesome-mcp-tools-mcp

list_trending

Get top MCP servers ranked by 24-hour star growth. Use limit parameter to control result count.

Instructions

Top MCP servers by 24h star growth.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trending"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	max results, 1-50 (default 20)

Output Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the ranking criterion (24h star growth) but omits details like sort order, pagination behavior, authentication needs, rate limits, or whether the list includes all servers or only a subset. This is insufficient for full informed use.

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 one-sentence description is succinct and starts with the key idea, containing no redundant words. It earns its place by immediately telling the user what the tool does, though its brevity comes at the cost of additional context.

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

Completeness2/5

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

The tool is simple with one optional parameter and an output schema, but the description lacks guidance on when to use it relative to sibling tools like list_hot. It also doesn't mention any prerequisites, limitations, or return behavior, leaving a new user uncertain about the tool's full context.

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?

The input schema fully documents the optional 'limit' parameter with a description and default value, so the description doesn't need to add more. However, the description also doesn't reinforce or clarify the parameter's meaning beyond what the schema already provides.

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?

The description 'Top MCP servers by 24h star growth' clearly conveys the tool's purpose: it returns a ranked list of servers based on their recent star growth. It specifies the resource (MCP servers) and the metric (24h star growth), which helps distinguish it from siblings like list_hot, although it doesn't explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as list_hot or list_tags. The description implies the use case (finding trending servers) but doesn't provide explicit conditions, exclusions, or mentions of when another tool would be more appropriate.

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

Deploy Server