Skip to main content
Glama

ai_get_import_history

Retrieve the import history of AI citation reports for a site, optionally filtered by report type, to track past imports and historical trends.

Instructions

Get history of imported AI citation 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_import_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL
reportTypeNoFilter by report type (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: no ordering, pagination, time window, or retention behavior for the history, and no indication of auth or scope requirements. Only the fact that it returns historical import records is conveyed.

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?

A single front-loaded sentence with no filler, though it errs toward terseness given the missing usage and return information. Nothing is wasted structurally, but brevity here reflects under-specification rather than efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 params, one required, no nesting, no output schema), yet without an output schema the description should indicate what a history entry looks like or how results are ordered/limited. It also omits any mention of the reportType filter's effect, leaving the agent unable to predict the response.

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%, including an enum for reportType, so the schema already explains both parameters and the baseline is 3. The description adds no extra meaning about how siteUrl scopes results or how the reportType filter affects the returned history.

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 uses a specific verb and resource ('Get history of imported AI citation reports'), which distinguishes it from the action-oriented sibling ai_import_citation_report. It stops short of explicitly contrasting itself with that sibling, so an agent must infer the read-only history-versus-import distinction.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, when not to, or which alternative to pick (e.g., ai_get_citation_trend or ai_import_citation_report). The only implicit cue is the word 'imported', leaving the agent to guess the context in which history is relevant.

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