Skip to main content
Glama

Citemark

Start tracking a website

start_tracking
Idempotent

Starts tracking a website in the user's Citemark account: sets up the questions buyers ask AI about its category and the competitors to compare it with, then asks AI assistants those questions on the account's schedule and shows the results on the Citemark dashboard. Needs the user's Citemark account; Claude asks them to connect it the first time. Does nothing if the website is already tracked.

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

Input Schema

NameRequiredDescriptionDefault
websiteYesThe product's website, like acme.com (a full URL works too).
categoryNoOptional: what kind of product it is, like 'uptime monitoring tool'. Read from the homepage when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, openWorld=true, idempotent=true, destructive=false), the description discloses that this kicks off ongoing scheduled work and dashboard output rather than a one-off fetch, plus the account-connection requirement and the idempotent no-op behavior in concrete terms. It does not cover cost/credits or how quickly results appear, so it stops short of a 5.

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 lead sentence is front-loaded with the action and the remaining clauses carry real information (side effects, account requirement, no-op condition) rather than filler. The middle clause is long and could be split, but nothing is redundant.

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 mutating setup tool with no output schema, the description covers the essential contract: prerequisites, side effects, and the already-tracked case. Details an agent might still want — what the call returns, latency before results exist, failure modes — are absent.

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 both parameters (website, category) are already documented in the schema, including the homepage-inference fallback for category. The description adds no parameter-level meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb+resource ('Starts tracking a website') and then spells out the concrete effect: generating category questions, competitor comparisons, and scheduled AI-assistant queries surfacing on the dashboard. That makes it clearly distinct from read-style siblings like get_my_tracking or get_ai_visibility, though it never names an alternative tool.

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?

It gives a genuine prerequisite ('Needs the user's Citemark account; Claude asks them to connect it the first time') and an exclusion condition ('Does nothing if the website is already tracked'), which tells the agent both when it can be called and when it is a no-op. What's missing is any routing guidance to a sibling for inspecting existing tracking instead.

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