Skip to main content
Glama

ADS Beast

competitor_ads_research

Read-only

Competitors in a niche and country with their headlines, angles and calls to action. The response says whether an item was observed in an ad library or inferred. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.UA
nicheNoBusiness niche or industry, in plain words.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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. The description adds two genuinely useful non-annotation facts: results are tagged as observed-in-ad-library versus inferred, and the call consumes 1 AI request. It still says nothing about latency, result volume, or what happens when niche is omitted despite being optional.

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?

Three short sentences with the deliverable front-loaded and the provenance note immediately after; nothing is padded. The clipped, verbless phrasing reads more like a field label than a sentence, but it costs no tokens.

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?

There is no output schema, and the description compensates by characterizing the response (headlines, angles, CTAs, observed vs inferred flag) and the cost model. For a read-only, open-world research call with three simple parameters, an agent has enough to select and invoke it correctly.

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 67% and geo/niche already carry their own descriptions, so the schema does most of the work. The description only echoes 'niche and country' and adds no format or behavior detail; client_id is undocumented in both places, leaving the tenancy/scope meaning of that parameter opaque.

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 names the resource concretely — competitors in a niche and country, plus the payload (headlines, angles, calls to action) — so an agent knows exactly what comes back. It stops short of a verb ('research'/'fetch') and never distinguishes itself from the many competitor_* siblings such as competitor_search_intel or competitor_social_signals.

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 explicit when-to-use statement, no prerequisites, and no named alternative among the crowded competitor_* family. Usage is only inferable from the phrase 'competitors in a niche and country,' which is not guidance so much as a restatement of the parameters.

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.