Skip to main content
Glama

Get the sources AI cites

get_top_sources
Read-onlyIdempotent

The sites (or pages) AI answers cite most for the project's prompts, with how many answers cite each, whether it's your site or a competitor's, and change vs the previous period. Use for "which sites does ChatGPT use for our category?" or "is our site cited?". Needs sign-in to Kliqo (read-only).

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

Input Schema

NameRequiredDescriptionDefault
kindNodomains
limitNo
modelNoOnly this AI model's answers; leave out for the project's current models
rangeNoDate range, ending today in the project's time zone30d
projectNoProject name, domain or id; leave out for the workspace's current project
end_dateNoExact end date (YYYY-MM-DD), today at the latest
start_dateNoExact start date (YYYY-MM-DD), for example the 1st of a month; use with end_date instead of range

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/not-destructive, so the safety profile is covered; the description adds the auth requirement ('Needs sign-in to Kliqo') and the comparison baseline ('change vs the previous period'). The parenthetical '(read-only)' largely restates the annotation, and scope/openWorldHint nuances aren't elaborated, so not a 5.

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?

Three tight sentences with the resource and returned metrics front-loaded, followed by use cases and prerequisites. Minor redundancy in restating 'read-only' after the annotations already say so.

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?

With an output schema present, the description need not explain return values, and it still summarizes them well. Auth requirement is disclosed; the only gaps are how range interacts with start_date/end_date and how the project default is resolved, both of which the schema partly covers.

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 71% and the enum-valued parameters (kind, model, range) are self-documenting. The description's 'sites (or pages)' phrasing hints at the kind switch and 'vs the previous period' hints at the range semantics, but it adds no real detail on limit, project, or start_date/end_date usage beyond what the schema states.

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 resource (the sites/pages AI answers cite) and enumerates the returned measures (citation counts, own vs competitor site, period-over-period change), so the tool's output is unambiguous. It does not explicitly differentiate itself from nearby siblings like get_ai_visibility or get_answers, which keeps it short of 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 Guidelines4/5

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

Two concrete example questions ('which sites does ChatGPT use for our category?', 'is our site cited?') give clear usage context, which is more than most definitions offer. However, no when-not-to-use guidance or named alternatives (e.g., use get_ai_visibility for overall visibility metrics) are given.

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