Skip to main content
Glama

Untrack Competitor

tubegrade_untrack_competitor
DestructiveIdempotent

Remove a channel from the user's tracked competitors in TubeGrade. The channel's public data is not affected. Removing a channel that isn't tracked changes nothing and says so.

Use only when the user asks to stop tracking or remove a competitor. Accepts a channel id (UC…), an @handle, or a channel URL.

Cost: 0 credits (free).

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": {
      "channel": "<channel>"
    },
    "name": "tubegrade_untrack_competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesThe tracked channel to remove — a channel id (UC…), an @handle, or a channel URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, and the description adds genuinely new context: the scope of destruction is limited to the tracking relationship ('the channel's public data is not affected'), the no-op case is surfaced to the caller, and the cost is stated as 0 credits. It does not describe auth/permission requirements, which is the remaining gap.

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?

Four short, front-loaded statements — effect, limitation, usage condition, accepted input, cost — with no filler or redundancy in the prose itself.

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 no explanation, and the description covers the operation's side effects, no-op behavior, input forms, and cost. Nothing an agent needs to invoke it correctly is missing.

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 100% and the single parameter already documents the accepted formats, so the description's restatement of channel id/@handle/URL adds no meaning beyond the schema. Baseline 3 is appropriate.

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 specific verb (remove/untrack) and resource (a channel from the user's tracked competitors), and its counterpart tubegrade_track_competitor in the sibling list makes the direction of the operation unambiguous.

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

Usage Guidelines4/5

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

'Use only when the user asks to stop tracking or remove a competitor' gives an explicit selection condition and implicitly excludes other cases. It never names tubegrade_track_competitor or tubegrade_my_competitors as the alternative, so the routing guidance stops just short of fully explicit.

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.

Resources