Skip to main content
Glama

get_trending_feed

Retrieve trending WebSim projects to discover popular community content, browse projects, and explore what's currently engaging users.

Instructions

Get trending WebSim projects feed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of projects to return (default: 20)
offsetNoNumber of projects to skip (default: 0)

Implementation Reference

  • MCP tool handler function for 'get_trending_feed' that invokes the API client method and formats the response as MCP content.
    handler: async (args) => {
      const { limit = 20, offset = 0 } = args;
      const result = await apiClient.getTrendingFeed(limit, offset);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            data: result,
            message: `Successfully retrieved ${result.items?.length || 0} trending projects`
          }, null, 2)
        }]
      };
    }
  • Input schema definition for the 'get_trending_feed' tool, defining optional limit and offset parameters.
    inputSchema: {
      type: "object",
      properties: {
        limit: {
          type: "number",
          description: "Number of projects to return (default: 20)",
          default: 20
        },
        offset: {
          type: "number",
          description: "Number of projects to skip (default: 0)",
          default: 0
        }
      }
    },
  • server.js:644-676 (registration)
    Tool registration object in the tools array, defining name, description, inputSchema, and handler for 'get_trending_feed'.
    {
      name: "get_trending_feed",
      description: "Get trending WebSim projects feed",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Number of projects to return (default: 20)",
            default: 20
          },
          offset: {
            type: "number",
            description: "Number of projects to skip (default: 0)",
            default: 0
          }
        }
      },
      handler: async (args) => {
        const { limit = 20, offset = 0 } = args;
        const result = await apiClient.getTrendingFeed(limit, offset);
        return {
          content: [{
            type: "text",
            text: JSON.stringify({
              success: true,
              data: result,
              message: `Successfully retrieved ${result.items?.length || 0} trending projects`
            }, null, 2)
          }]
        };
      }
    },
  • Core API client helper method that makes the HTTP request to fetch the trending feed from WebSim API.
    async getTrendingFeed(limit = 20, offset = 0) {
      const params = new URLSearchParams({ limit: limit.toString(), offset: offset.toString() });
      return this.makeRequest(`/api/v1/feed/trending?${params}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Get' which implies a read operation, but doesn't disclose behavioral traits like rate limits, authentication needs, or what 'trending' entails (e.g., algorithm, time frame). This is inadequate for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (simple read operation with two parameters), 100% schema coverage, and no output schema, the description is minimally adequate. However, it lacks details on behavioral aspects and sibling differentiation, which could improve completeness for agent use.

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%, with clear descriptions for 'limit' and 'offset' parameters. The description doesn't add any meaning beyond the schema, such as explaining how 'trending' might affect pagination, so it meets the baseline for high coverage without extra value.

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 clearly states the verb 'Get' and the resource 'trending WebSim projects feed', making the purpose understandable. However, it doesn't differentiate from siblings like 'get_posts_feed' or 'search_feed', which might also retrieve feeds, so it's not fully specific to sibling context.

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 provided on when to use this tool versus alternatives such as 'get_posts_feed' or 'search_feed'. The description only states what it does without context, leaving the agent to infer usage based on tool names alone.

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/gigachadtrey/websimm'

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