StealAds

Analyze a competitor’s ads

get_competitor_analysis

Read-onlyIdempotent

Summarizes the stored ads of one saved competitor: its most common hooks, angles and funnel stages, plus its longest-running ads. For understanding a competitor's overall approach; list_tracked_rival_ads returns the individual ads and get_playbook the written recommendations. Counts cover only the ads StealAds has stored for that competitor, not its complete advertising.

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": {
      "competitor_id": "<competitor_id>"
    },
    "name": "get_competitor_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`competitor_id`	Yes	Competitor id from list_competitors.
`response_format`	No	Output format: text (default), json, or table, which returns the longest-running ads of this same summary as CSV without fetching more rows.

Output Schema

Name	Required	Description
`as_of`	No	as of value in this response.
`scope`	No	Which accessible ad examples this search covered.
`top_ads`	No	top ads value in this response.
`patterns`	No	Observed hook and message patterns in the selected rival sample.
`total_ads`	No	Ads stored in this tracked competitor set, not an advertiser or library total.
`analyzed_ads`	No	Analyzed ads within this stored tracked set only.
`competitor_id`	No	Reference for the selected rival.
`tracking_note`	No	tracking note value in this response.
`competitor_name`	No	competitor name value in this response.
`longest_running`	No	longest running value in this response.
`tracking_enabled`	No	tracking enabled value in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / response_format / description

Previous value: -"table returns CSV for the same bounded tracked-ad summary; no additional rows are fetched."New value: +"Output format: text (default), json, or table, which returns the longest-running ads of this same summary as CSV without fetching more rows."

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's real contribution is the data-coverage caveat: counts reflect only ads StealAds has stored for that competitor, not its complete advertising. That is a substantive disclosure about result trustworthiness. It does not discuss caching or refresh timing, keeping it a step below fully rich.

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?

Three sentences, each doing distinct work: what it returns, when to use it versus alternatives, and the coverage limitation. The core purpose is front-loaded and nothing is repeated from the title or schema.

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?

For a single required identifier plus a format enum, with an output schema handling return values and annotations covering safety, the description supplies everything an agent needs: scope, alternatives, and the caveat that results are derived from stored data only.

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 100%, and the schema itself documents competitor_id sourcing and the enum meaning, including that table returns the same summary's longest-running ads as CSV without extra fetching. The description adds no parameter detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (summarizes) and resource (stored ads of one saved competitor), then enumerates the exact dimensions produced: hooks, angles, funnel stages, and longest-running ads. It explicitly distinguishes itself from list_tracked_rival_ads (individual ads) and get_playbook (written recommendations).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the selecting condition plainly — 'For understanding a competitor's overall approach' — and routes the agent to the two named alternatives with the reason each exists. No inference about when to prefer this tool is left to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All StealAds tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.