Skip to main content
Glama

Visibility Genies

Create a rank tracker

create_rank_tracker

Create a rank tracking configuration for a project. Creating an empty tracker buys nothing and starts no check. A daily, weekly or monthly tracker buys its checks once it has keywords, and only after the user approves its price on the tracker's page. The domain defaults to the project's domain; market defaults to the project's market; devices default to mobile, search depth to 40, AI Overviews to checked, and schedule to manual; re-adding an archived tracker keeps its own devices, depth and AI Overviews unless they are given, and brings back its keywords: the reply prices them, and a scheduled one stays paused, buying nothing, until the user approves that price on the tracker's page. Use estimate_rank_tracker_cost before adding keywords to a scheduled tracker or starting a live run. Call get_rank_tracker first to avoid duplicates.

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

Input Schema

NameRequiredDescriptionDefault
domainNoDomain to track. A hostname or URL is accepted and stored normalized. Defaults to the project's domain.
devicesNoDevices to track. Defaults to mobile for a new tracker; a re-added archived tracker keeps its own unless this is given.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
serpDepthNoNumber of Google results to inspect. Defaults to 40 for a new tracker; a re-added archived tracker keeps its own unless this is given.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
locationNameNoCity or region name for local rank tracking.
checkAiOverviewsNoWhether each check waits for the AI Overview Google loads after the results and records whether it cites the domain. Defaults to true for a new tracker, as in the app; a re-added archived tracker keeps its own setting unless this is given. It raises each check's price, up to double at the default depth, which estimate_rank_tracker_cost includes; without it only AI Overviews already cached are seen.
scheduleIntervalNoCheck schedule. Defaults to manual so creating a tracker cannot cause future spend. A scheduled tracker buys nothing until it has keywords and the user approves its price on the tracker's page.

Output Schema

NameRequiredDescriptionDefault
metaNo
configYes
trackerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Well beyond the annotations (which only declare a non-read-only, non-destructive, closed-world mutation). The description discloses the spend model — checks are purchased once keywords exist and only after the user approves a price on the tracker page — plus that a scheduled re-added tracker stays paused until approved, and that AI Overviews up to doubles check price. This is the billing/consent contract an agent cannot infer from the structured fields.

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?

Front-loaded and information-dense, but the core is a single semicolon-chained sentence running across several distinct behaviors (defaults, re-add rules, pricing, approval gating), which is hard to parse. The default-value list also duplicates what the input schema already states, so some sentences do not fully earn their place.

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?

For a billable, consent-gated creation tool with an output schema present, the description covers the full lifecycle: defaults, re-add semantics, what triggers spend, what blocks spend, and which sibling to call before and after. Nothing material an agent needs to invoke this 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%, so the baseline is 3. The description largely restates schema-documented defaults (domain, market, mobile devices, depth 40, AI Overviews checked, manual schedule) rather than adding new meaning; the one genuinely additive point is the re-add behavior where archived devices/depth/AI Overviews are preserved unless supplied, which the schema also mentions. languageCode is not addressed at all in the prose.

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 ('Create a rank tracking configuration for a project') and immediately clarifies the scope boundary: an empty tracker 'buys nothing and starts no check.' It also distinguishes itself from get_rank_tracker, estimate_rank_tracker_cost and the keyword tools by name, so an agent can separate it from siblings without opening a schema.

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?

Explicit routing guidance: 'Call get_rank_tracker first to avoid duplicates' and 'Use estimate_rank_tracker_cost before adding keywords to a scheduled tracker or starting a live run.' It also states a negative case (creating an empty tracker is pointless), which is exactly the when-not-to-use information an agent needs.

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