Skip to main content
Glama

Change what is tracked

manage_tracking
Destructive

Change the tracked questions and competitors, or scan now. Plan quotas apply. operation: add_prompts = track new questions (prompts, topic); archive_prompts = stop scanning, keep history (prompts); remove_prompts = remove from the list (prompts); add_competitor = track a competitor by name or URL (competitor); remove_competitor = stop tracking a competitor (competitor); run_scan = scan the questions on the AI engines now (plan cadence). Without confirm: true NOTHING changes: you get a preview. Show it to the user and call again with confirm: true only after they approve it.

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

Input Schema

NameRequiredDescriptionDefault
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.
topicNoOnly for operation add_prompts. Optional topic to file them under.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
promptsNoOnly for operation add_prompts, archive_prompts, remove_prompts. Buyer questions to track, 1 to 25.
operationYesWhat to do.
competitorNoOnly for operation add_competitor, remove_competitor. Competitor name or URL, e.g. "Notion" or "https://notion.so".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations flag the tool as destructive, non-idempotent and open-world, and the description goes well beyond them: it discloses the mandatory preview-then-confirm safeguard, that 'archive_prompts' stops scanning but retains history (versus 'remove_prompts' which drops from the list), and that plan quotas apply. These are exactly the mutation-safety details an agent needs before calling.

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?

The description is dense and front-loaded, with the enumeration of operations followed by the critical confirm rule at the end where it will be read last before calling. It does duplicate the operation-to-parameter mapping already present in the schema field descriptions, which is minor waste but not harmful.

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?

For a six-operation mutation tool with no output schema, the description covers the operation set, the destructive semantics, the confirm gate, and quota constraints. It does not describe what the preview response actually contains, which slightly weakens the instruction to 'show it to the user'.

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 per-parameter notes ('Only for operation add_prompts...') already carry the operation-to-parameter mapping that the description repeats. The description adds the 1-to-25 prompt bound context and quota mention, but does not meaningfully extend parameter meaning beyond the schema, 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 opening sentence names a specific verb and resource (tracked questions and competitors) and then enumerates all six operations with the payload each one takes. An agent can immediately tell this is the write-side counterpart to read tools like get_prompts without opening the schema.

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?

Each operation is scoped to what it does, 'run_scan' is distinguished from list mutations by noting plan cadence, and the confirm/preview protocol is spelled out as a two-step flow with an explicit approval gate. The only gap is that no sibling alternative is named (e.g. use get_prompts to read the current list), so the routing guidance is contextual rather than 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.