Skip to main content
Glama

ADS Beast

competitor_search_intel

Read-only

Searches the web for a competitor's ads, positioning, pricing, selling points and reviews.

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

Input Schema

NameRequiredDescriptionDefault
nicheNoBusiness niche or industry, in plain words.
aspectNoads, pricing, reviews, positioning or all.all
client_idNo
competitor_domainNoCompetitor's domain.

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?

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety and open-web behavior are covered. The description adds the research aspects it searches for, but it does not state what kind of results are returned, how sources are selected, or any limitations of the web search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler. Every phrase identifies the resource scope, and nothing is repeated unnecessarily.

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?

This is an open-world research tool with four parameters, no output schema, and many close siblings, so the description should do more. It omits return behavior, source scope, parameter relationships, and explicit routing to alternatives, leaving significant gaps for an agent selecting and invoking it.

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 75%, so most parameters already carry their own meaning. The description restates the aspect categories, but it does not explain niche, client_id, competitor_domain, or how those inputs combine; it also adds 'selling points' while the enum uses 'all'.

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 gives a specific verb, 'Searches the web', and a clear resource, a competitor's ads, positioning, pricing, selling points and reviews. It is understandable without opening the schema, though it does not differentiate from close siblings like competitor_ads_research or competitor_site_analyze.

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?

The coverage list implies this is the broad competitor-intelligence search tool, so a reader can infer when it is relevant. However, it gives no explicit when-to-use guidance, no exclusions, and no routing against the many competitor-related siblings.

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.