Skip to main content
Glama

ai_get_citation_trend

Track citation trends over time from imported AI Performance Overview reports to see how AI citations change and support reporting decisions.

Instructions

Get citation trend over time from imported AI Performance Overview reports.

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": "ai_get_citation_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the useful constraint that data comes only from previously imported reports (implying empty/error results when no import exists), but says nothing about the time granularity of the trend, permissions, or result shape. That is partial disclosure for a read-style analytics tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the scope constraint attached and zero filler. Nothing is redundant or padded.

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 single-parameter, no-output-schema tool this is close to complete: it identifies the resource and the source dataset. It could add the date-range assumption or trend granularity, but no critical calling information 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 coverage is 100% for the single 'siteUrl' parameter, so the schema already defines it and the description adds no format, scoping, or multi-site meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get citation trend over time') and names the data source ('imported AI Performance Overview reports'), which separates it from sibling list-style tools like ai_get_top_cited_pages. It does not explicitly name the sibling it differs from, keeping it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'from imported AI Performance Overview reports', which hints at a prerequisite (a report must be imported first, via ai_import_citation_report), but no when-to-use vs. alternative guidance is stated. An agent must infer that it should call this for time-series trends rather than for top-N rankings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.