Skip to main content
Glama

ADS Beast

aeo_mention_opportunities

Read-only

Fresh discussions where people ask for recommendations in a client's niche, with a suggested 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": "aeo_mention_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful context beyond that: results include a suggested reply, and crucially the cost signal "AI: 1 AI request," which matters for a metered tool. It stops short of saying where discussions come from or how "fresh" is determined.

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 compact sentence plus a terse cost note; nothing is padded. The "AI: 1 AI request" fragment is telegraphic but front-loads an important operational fact efficiently.

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?

With no output schema, the description carries the burden of describing return values, and it only partially does so (discussions plus suggested reply). A two-parameter read tool is simple enough that this is near-adequate, but the data source, freshness definition, and result shape remain underspecified.

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 coverage is 50%: limit is documented in the schema, while client_id has no description. The phrase "in a client's niche" hints that client_id scopes results to one client, which adds a little meaning, but neither the freshness window nor the default limit semantics are clarified.

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 description conveys a resource shape ("fresh discussions where people ask for recommendations in a client's niche, with a suggested reply") but never states a clear verb and never distinguishes this from sibling tools such as reddit_opportunities or analytics_growth_opportunities. An agent can infer it discovers recommendation-seeking threads, but the scope boundary is not stated.

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 when-to-use guidance, no prerequisites, and no mention of alternatives for the closely related opportunities tools. The only context is the implicit scope of a client's niche, leaving the agent to guess at selection criteria.

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.