Skip to main content
Glama

ADS Beast

competitor_list

Read-only

Competitors on record with site, niche, collected ads and keywords.

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

Input Schema

NameRequiredDescriptionDefault
with_adsNoInclude the collected ads (larger response).
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. Beyond that, the description adds almost nothing: it does not say what the listing is scoped to, whether results are paginated or bounded, or how expensive the with_ads variant is in practice.

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?

It is short and front-loaded with the resource name, but it is an incomplete sentence fragment rather than a structured statement of action, scope and return. No words are wasted, but too much is omitted for the size to be a virtue.

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?

With two parameters, no output schema and an undocumented client_id, the description needs to explain scoping and return shape, and it does neither. The field list partially compensates, but an agent cannot determine from this text whether results are per-client or global.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: with_ads is documented in the schema, but client_id is undocumented everywhere, and the description gives no clue whether client_id filters competitors to a given client. The phrase 'collected ads' loosely alludes to with_ads but adds no meaning beyond the schema text.

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 identifies the resource (competitors) and hints at returned fields (site, niche, collected ads and keywords), but there is no verb and no scope statement, so it reads like a noun phrase rather than a defined operation. It does not distinguish this listing from sibling research tools such as competitor_site_analyze or competitor_ads_research.

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 guidance on when to call this versus the many other competitor_* and list_* siblings. The only hint is the parenthetical in the schema about with_ads producing a larger response, which the description itself never mentions.

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.