Skip to main content
Glama

Get engagement feed

get_engagement_feed
Read-onlyIdempotent

Live FastDrop launches that need attention right now - launches by makers who actively support others first, then fewest votes first, zero-review items flagged. The participation loop: Vote on, review, or comment on 3 different launches in the last 7 days: your live launches are shown first to other makers in the engagement feed (get_engagement_feed), and a submission still in manual review moves to the front of the queue. With auth, the feed is personalized (your own launches and already-voted items excluded, tag-matches with your launches ranked first), each item says whether it needs a vote (toggle_vote) or a review (post_review), and the boost object reports your progress. Unauthenticated callers get the generic feed.

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": "get_engagement_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-20, default 5

Output Schema

NameRequiredDescriptionDefault
boostNo
launchesYes
personalizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavior beyond that: personalization only when authenticated, exclusion of your own and already-voted items, tag-match ranking, per-item vote/review flags, a boost progress object, and a generic feed for unauthenticated callers. It stops short of describing pagination or how 'needs attention' is thresholded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, which is good. But the middle section explains the site's participation incentive loop (vote on 3 launches in 7 days, your launches get shown first, manual review jumps the queue) — marketing/mechanics that are only marginally actionable for tool invocation. The final sentence about unauthenticated callers would be more usefully placed next to the personalization claim.

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?

For a read-only feed with one optional parameter and an output schema, the definition covers what the agent actually needs: auth-dependent behavior, ranking rules, per-item action hints pointing at toggle_vote and post_review, and the boost object. Missing only minor operational detail such as pagination or how many items a typical feed returns.

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 single `limit` parameter is fully documented in the schema (coverage 100%), including range 1-20 and default 5, so the description carries no extra burden here. It never mentions limit, ordering guarantees tied to limit, or whether the ranking applies before truncation. Baseline 3 is appropriate when the schema does the work.

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 first sentence states a specific verb+resource: it returns live FastDrop launches needing attention, plus the ranking rule (supportive makers first, fewest votes first, zero-review flagged). That is far more specific than a name restatement. It never names a sibling tool (e.g., list_launches) as the alternative, so the boundary is only inferable from the 'needs attention' framing.

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

Usage Guidelines3/5

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

Usage is implied by 'launches that need attention right now' and by the participation-loop explanation, which tells the agent why a maker would want this feed. It also splits authenticated vs unauthenticated outcomes, which is genuinely useful context. However, there is no explicit when-not-to-use guidance and no named alternative among list_launches, find_deals, or search_products.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources