Skip to main content
Glama

ai_import_citation_report

Import Bing Webmaster Tools AI citation reports from CSV or XLSX files and automatically detect PageStats, Overview, or SearchQueries format for analysis.

Instructions

Import an AI citation report (CSV or XLSX) exported from Bing Webmaster Tools AI Performance section. Automatically detects report type (PageStats, Overview, or SearchQueries).

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

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL this report belongs to
filePathYesPath to the CSV or XLSX file to import

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose genuine behavior beyond the schema: accepted file formats and automatic detection of report type (PageStats, Overview, SearchQueries). However, it omits write semantics that matter for an import: whether a re-import replaces or duplicates existing data, permission/site-listing requirements, and failure behavior for unrecognized files.

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?

Two sentences, zero waste, with the core action and source front-loaded and the auto-detection detail following. Nothing is redundant with the title or schema.

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

Completeness3/5

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

For an import tool with no annotations and no output schema, the definition covers what the tool reads but not what it does downstream: no statement of what gets stored, what the response contains, or how duplicate/overlapping imports are handled. Adequate to invoke, incomplete for understanding consequences.

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 both parameters are already documented in the schema. The description adds only marginal meaning: it clarifies that filePath should point to a BWT-exported AI citation report and that siteUrl ties the report to a site. Baseline 3 is appropriate.

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 gives a concrete verb+resource ('Import an AI citation report'), plus the accepted formats (CSV/XLSX) and the exact upstream source (Bing Webmaster Tools AI Performance section). The import verb inherently distinguishes it from the get_/bing_get_ read-only siblings, though no sibling is named explicitly (e.g., ai_get_import_history).

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 the source constraint: use it on a file exported from the BWT AI Performance section. There is no explicit when-to-use versus alternatives (e.g., ai_compare_with_bing_stats for live comparison), no prerequisites such as site ownership or API configuration, and no guidance on repeat/duplicate imports.

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