Skip to main content
Glama

Track where an article ranks

flypost_track_article_keywords

The article keyword tracker (Analytics > Article rankings, a beta some accounts have): add the searches an article should rank for and its live URL, and check whether it appears in Google's top 10, Google's AI Overview, ChatGPT and Perplexity (each sampled several times). New keywords are checked straight away in the background (several minutes); call again with check false to read the results. Returns every tracked keyword with its latest result per engine.

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

Input Schema

NameRequiredDescriptionDefault
checkNoDefault true: run a check for keywords not yet checked.
keywordsNo
article_idYes
country_codeNoGoogle country for new keywords, e.g. 'gb'. Default 'us'.
published_urlNoThe live URL of the published article (required before anything can be checked).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds meaningful behavior beyond that: the feature is a beta available on some accounts, checks are queued in the background and take several minutes, each engine is sampled several times, and results are stored so a later call can retrieve them. That async/storage model is exactly what an agent needs to avoid polling wrongly or assuming an immediate answer.

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?

One dense but front-loaded paragraph: what it is, how to use it, what comes back. Every clause carries information (availability caveat, engines, timing, return shape). It runs long for a single sentence and could be split into usage and returns, but nothing is filler.

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?

With no output schema, the description still closes the loop by saying it returns every tracked keyword with its latest result per engine, and it explains the async delay so an agent won't misread an empty result. For a 5-parameter, non-destructive tracking tool, nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, and the description fills the gap that matters most: it explains what the keywords actually are (the searches the article should rank for), that published_url is the live URL required before checking can happen, and that check=false reads prior results — semantics beyond the terse schema notes. Only country_code goes unmentioned in the prose, which keeps this from a 5.

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 names a specific verb and resource ('article keyword tracker' that checks rankings across Google top 10, AI Overview, ChatGPT, Perplexity) and locates it in the product ('Analytics > Article rankings'). An agent can distinguish this from the sibling generation/editing tools without opening the schema, though it never explicitly contrasts with another 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 concrete sequencing guidance: add keywords plus the live published URL, new keywords are checked asynchronously, then 'call again with check false to read the results.' That is clear when-and-how guidance. It stops short of stating exclusions or prerequisites such as what to do if no URL exists yet, which the schema only gestures at.

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.