Skip to main content
Glama

list_citation_lifetimes

Read-only

Which cited pages (or domains) are losing or gaining AI citations: each one's citation-lifetime status over the last 26 completed ISO weeks (lost, fading, ended, regained, new, rising, first_measured, no_recent_data, steady, occasional) with its rate before and now, n for each, first and last citation, weeks cited and streaks, sorted by the size of the rate change. Filters: scope (own, competitors, all), status, granularity (page or domain), source, limit (default 25, max 200). statusCountsAllPages counts every page, including those not listed. One page's lifetime, with its weekly series and causes, is in get_cited_url. The eligibility, status and refresh rules arrive in howToRead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_citation_lifetimes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 25, max 200).
scopeNo"own" (default) = the client's own domains, "competitors" = the tracked competitors' domains, "all" = every cited page.
sourceNoData source: "blended" (default — CrunchJunkie scans plus imported Peec data, an engine both track counted once with the CrunchJunkie scan winning), "native" (CrunchJunkie scans only) or "peec" (imported Peec data only).
statusNoOnly these statuses, e.g. ["lost", "fading"] ("occasional" pages are counted, never listed).
clientIdNoClient id — uses the AI-Visibility project its Overview opens in the app (the newest).
projectIdNoAI-Visibility project id.
granularityNo"page" (default) or "domain".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Data source: \"blended\" (default — your scans plus imported Peec data, an engine both track counted once with your scan winning), \"native\" (your scans only) or \"peec\" (imported Peec data only)."New value: +"Data source: \"blended\" (default — CrunchJunkie scans plus imported Peec data, an engine both track counted once with the CrunchJunkie scan winning), \"native\" (CrunchJunkie scans only) or \"peec\" (imported Peec data only)."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive behavior; the description adds substantial context: the 26-week window, sorting by rate change, statusCountsAllPages counting unlisted pages, and the rule that occasional pages are counted but never listed.

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 definition is dense but front-loaded around the resource and its output shape, with filters and alternatives following. It is long, but most detail is useful for a complex listing tool.

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?

Given no output schema, the description supplies the key return characteristics: statuses, rate before/now, n, first/last citation, weeks cited, streaks, sorting, and statusCountsAllPages behavior. It also explains where deeper rules live.

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 coverage is 100%, so the schema already documents all seven parameters, including enums and defaults. The description reinforces filter names and default/max limit values but adds little parameter syntax beyond the schema.

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, explains exactly what the listing contains (citation-lifetime status, rates, counts, dates, streaks), and distinguishes it from get_cited_url for single-page detail.

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?

Explicitly routes single-page investigation to get_cited_url, names the available filters, and points to howToRead for eligibility/status/refresh rules. The alternatives and context are clear.

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