Skip to main content
Glama

Track a competitor in Kliqo

track_competitor
Destructive

Add a competitor to the project's tracked brands (name and website), so Kliqo measures it in every answer. Use when AI keeps naming a brand the member doesn't track yet (get_ai_visibility lists them). Confirm with the member first. Editors, admins and owners only.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
domainNoIts website, for example acme.com
projectNoProject name, domain or id; leave out for the workspace's current project

Output Schema

NameRequiredDescriptionDefault
statusYes

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=true and idempotentHint=false; the description adds valuable context beyond them by stating the role restriction (editors, admins, owners only) and the confirmation requirement. It does not clarify duplicate handling or what exactly is affected, which would fully close the loop on the destructive/idempotent hints.

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?

Three short sentences, front-loaded with the action and followed by the trigger, the confirmation rule and the permission gate. Efficient, though the permission note could arguably ride on annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need no explanation, and the description covers trigger, confirmation and authorization. The main remaining gap is duplicate/idempotency behavior for an add operation, which matters given idempotentHint=false.

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?

With 67% schema coverage, the schema already documents domain and project. The description restates 'name and website' but adds no format or constraint detail, and never mentions the project parameter's override behavior. 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 and resource ('Add a competitor to the project's tracked brands') and explains the effect ('so Kliqo measures it in every answer'). It is clearly distinguishable from siblings, naming get_ai_visibility as the discovery source.

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?

Gives an explicit trigger ('Use when AI keeps naming a brand the member doesn't track yet'), points at the sibling that surfaces those brands, and adds the required confirmation step with the member. Nothing left to inference.

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