AlphaWeb

competitors_save

Destructive

Edit profiles/accounts. Monitoring requires MCP confirmation; verification is platform-owned.

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": {
      "workspace": "<workspace>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "competitors_save"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`role`	No
`notes`	No
`domain`	No
`remove`	No
`country`	No
`workspace`	Yes
`competitor`	No
`monitoring`	No
`approval_token`	No
`add_ad_accounts`	No
`idempotency_key`	Yes
`remove_ad_accounts`	No
`update_ad_accounts`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.6/5.0

Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is lower. The description adds real context that monitoring changes require MCP confirmation and that verification is platform-owned, but it omits that `remove`/`remove_ad_accounts` delete data and says nothing about idempotency behavior.

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?

Two short sentences with no filler and the purpose is front-loaded, but the brevity comes from under-specification rather than tight editing. It doesn't earn its place given how much a 14-parameter destructive tool needs.

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?

A destructive, 14-parameter mutation with no output schema and zero parameter descriptions should be doing far more. An agent has no way to learn from this description how profile edits differ from ad-account edits, or what a successful save returns.

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 description coverage is 0% across 14 parameters, so the description must compensate and it largely doesn't. Only `monitoring` is obliquely referenced (confirmation requirement); `remove`, `role`, `approval_token`, and the three ad-account arrays are undocumented in both places.

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?

"Edit profiles/accounts" gives a verb plus a loosely named resource, but never says this saves competitor/brand profiles and their ad accounts. Nothing distinguishes it from sibling tools like competitor_settings_save, competitor_signals_update, or competitor_ads_update.

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 settings_* save tools, and no note on required order (e.g. obtaining an approval_token first). The one usage hint (monitoring requires MCP confirmation) is about mechanics, not tool selection.

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

All AlphaWeb 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?