Skip to main content
Glama

ADS Beast

competitor_site_analyze

Read-only

Reads one competitor site: selling points, prices, technology, pixels, call-to-action patterns and audience signals.

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": {
      "url": "<url>",
      "client_id": "<client_id>"
    },
    "name": "competitor_site_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// page URL.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 safety and external-network access are covered. The description usefully adds the categories of data extracted, but says nothing about crawl cost, rate limits, failure modes, or how client_id scoping affects the read.

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?

A single front-loaded sentence with no filler; the resource comes first and the extracted facets follow. It is compact and easy to parse, though a brief usage clause could be added without bloat.

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 list of analyzed facets is doing double duty as a hint about results, which is helpful. However, the undocumented client_id and the absence of any alternative-routing guidance leave real gaps for a tool with this many overlapping siblings.

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%: url is documented ('https:// page URL'), while client_id has no description anywhere. The description never mentions either parameter and does not explain what client_id scopes or whether the URL must be a homepage or a specific page, so it fails to compensate for the coverage gap.

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?

'Reads one competitor site' gives a specific verb and resource, and the enumeration of extracted dimensions (selling points, prices, technology, pixels, CTA patterns, audience signals) makes the scope concrete. It does not differentiate itself from nearby tools such as competitor_ads_research or seo_competitor_analysis, so it stops short of a 5.

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?

The phrase 'Reads one competitor site' implies single-URL scope, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many competitor_* siblings. The agent must infer routing from the tool name alone.

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.