Skip to main content
Glama

Rank Checker by GSC Wizard

List Rank Checker keyword sets

list_rank_keyword_sets
Read-only

Use this when the user asks which keywords they track in the Rank Checker, or before reading or adding to a keyword set. Returns every Rank Checker keyword set on a property, whoever on the team made it (createdByYou says whether the caller did): each set's id, name, country and device (null = all), alert settings, keyword count, the summary of its last daily check (average position, top 3 / top 10 counts, keywords ranking, improved and declined over the last 7 days) and when it was checked. Not for the positions themselves: use get_rank_keyword_data with a set id; to create a set or add keywords use add_rank_keywords.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlYes

Output Schema

NameRequiredDescriptionDefault
setsNo
siteUrlNo
nextStepNo
emptyBecauseNo
methodLimitsNo

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 readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is free. The description adds genuine behavioral context beyond that: results span the whole property regardless of creator, and the createdByYou flag tells the caller about their own authorship. It stops short of noting pagination or ordering, but 'Returns every ... set' implies no pagination is needed.

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 usage trigger is front-loaded in the first clause, followed by scope, then the field inventory, then the sibling routing. It is fairly dense — the parenthetical about last-daily-check summary fields is a long clause — but no sentence is filler, and each block has a job.

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?

An output schema exists, so the enumerated return fields are somewhat redundant, yet they usefully tell an agent what to expect at a glance. Usage, scope and alternatives are all covered. The only real gap is the siteUrl value format, which neither schema nor description pins down.

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?

There is one parameter (siteUrl) with 0% schema description coverage, so the description carries the burden. It hints at the parameter's meaning by saying results are scoped 'on a property', but never names siteUrl or states its expected format (full URL vs. domain vs. identifier). Partial compensation only.

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 ('List Rank Checker keyword sets') and immediately narrows scope ('every Rank Checker keyword set on a property, whoever on the team made it'). It also names the sibling that returns the thing this does not (get_rank_keyword_data) and the one that mutates (add_rank_keywords), so the tool is distinguishable without opening any 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?

Gives explicit triggers ('when the user asks which keywords they track', 'before reading or adding to a keyword set') plus explicit exclusions with named alternatives ('Not for the positions themselves: use get_rank_keyword_data with a set id; to create a set or add keywords use add_rank_keywords'). Both the when and the when-not are covered.

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.