Skip to main content
Glama

ADS Beast

reddit_mentions_monitor

Read-only

New Reddit threads mentioning a client's brand, keywords or competitors, with sentiment and a draft reply. AI: 1 AI request.

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_mentions_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 is covered. The description adds genuinely useful context beyond that — that each call returns sentiment and a draft reply and costs '1 AI request' — but leaves the meaning of 'new' undefined (since last run? past 24h?) and gives no sense of volume or pagination.

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?

Two compact, front-loaded sentences with no filler; the output contents are stated before the cost note. The terse 'AI: 1 AI request' tag is slightly cryptic in format but earns its place as a cost signal.

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

Completeness5/5

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

For a one-parameter, read-only, no-output-schema tool, the description supplies what an agent actually needs: what is returned (threads, sentiment, draft reply) and the cost of the call.

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?

With a single parameter at 0% schema description coverage, the description must compensate, and it only indirectly does: it implies brand, keywords and competitors drive the query, but the sole input is client_id, and the description never confirms that those settings are read from client configuration rather than passed in.

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 uses a specific verb-resource pairing ('New Reddit threads mentioning a client's brand, keywords or competitors') and names the payload (sentiment plus draft reply), so the agent knows exactly what it retrieves. It does not, however, distinguish itself from siblings like reddit_opportunities or reddit_reply_draft, which could plausibly return overlapping content.

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 only implied by the word 'monitor' and the mention-tracking framing; there is no explicit statement of when to call this versus reddit_opportunities or reddit_reply_draft, and no prerequisites (e.g., whether the client must already have keyword/competitor config) are stated.

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.