Mark

Remove Competitor Lookup

remove_competitor_lookup

Destructive

Removes an untracked domain from Other lookups on the competitor scorecard, in every market: deletes its unstarred competitor record and every stored lookup of it. Looking it up again runs a new lookup, and tracking it again starts fresh. Refuses a tracked competitor (untrack it first) and your own sites. A domain with nothing stored removes nothing. Related: list_competitors, untrack_competitor.

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": {
      "domain": "<domain>"
    },
    "name": "remove_competitor_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain to remove, like example.com.

Output Schema

Name	Required	Description	Default
`domain`	Yes
`removedLookups`	Yes
`removedCompetitor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructive/non-idempotent, but the description adds substantive behavior: it deletes both the unstarred competitor record and every stored lookup across all markets, is effectively a no-op when nothing is stored, and refuses tracked domains. This is exactly the kind of consequence detail annotations can't convey.

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?

Effects are front-loaded, followed by reversibility, refusal conditions, and the no-op case, then a Related line. Each sentence carries distinct operational information with no filler.

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?

An output schema exists so return values need not be described; the description instead covers scope, side effects, refusal cases, and the empty-state case. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% with an example (example.com), so the baseline is 3; the description adds qualification that the domain must be untracked and not a site you own, which narrows valid input meaningfully.

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?

States a precise verb+resource (remove an untracked domain's competitor lookup) plus scope ("in every market") and the exact records deleted. It clearly distinguishes itself from untrack_competitor and the delete_*/list_* siblings by naming what it does not touch (tracked competitors, own sites).

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?

Explicit when-not conditions: refuses a tracked competitor (untrack first) and refuses your own sites, and explains that re-looking-up or re-tracking starts fresh. It also names related tools (list_competitors, untrack_competitor), so the agent knows the routing alternatives.

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

All Mark 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.

Resources

Need Help?