Skip to main content
Glama

ADS Beast

reddit_opportunities

Read-only

Buyer-intent Reddit threads in a client's niche, ranked.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>"
    },
    "name": "reddit_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 safety and external-data reach are covered structurally. The description adds only that output is ranked and niche-scoped; it says nothing about ranking criteria, result volume, time window, or whether live Reddit data is queried, which is the useful leftover context for an open-world tool.

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?

One short, front-loaded sentence with zero filler. Its brevity is efficient, though it borders on under-specification rather than ideal conciseness.

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?

There is no output schema and no annotations describing returns, yet the description never explains what a 'ranked' result contains, how many items come back, or over what period opportunities are gathered. For an open-world discovery tool, that leaves the agent guessing about both invocation intent and result shape.

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 0%, so the description must compensate for the single undocumented client_id parameter. It partially does by indicating the client supplies the 'niche' used for targeting, which is real meaning beyond the schema, but it never says whether client_id is required or how it scopes results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'Buyer-intent Reddit threads in a client's niche, ranked' does convey the resource (Reddit threads), the filtering concept (buyer intent, client niche) and that results are ordered, but it has no verb and never states what the tool actually does with them (find? score? draft?). It is clearer than the bare title but does not distinguish it from siblings like reddit_mentions_monitor or reddit_amplification_plan.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternative. The phrase 'buyer-intent' hints at a use case but the agent must infer it entirely.

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.