Skip to main content
Glama
Sign In

CiteLadder

by com.citeladder
OverviewDiscussionsAdmin

Show AI visibility

render_visibility
Read-onlyIdempotent

Show the user an interactive visibility view, in clients that display apps: overview, trends over a window, or cited sources for one run. To reason over the numbers yourself, use read_visibility_overview, read_visibility_trends or read_visibility_sources.

Input Schema

NameRequiredDescriptionDefault
viewNoWhich view to show; each other field says the views it applies to.overview
levelNoSources only: domain lists publishers (the default); url lists pages.domain
limitNoSources only: rows per page.
to_atNoTrends only, required there: end of the window.
cohortNocore is the scored prompts (the default); comparison is reported separately.core
cursorNoSources only: the next_cursor a previous page returned.
domainNoSources only: a cited domain such as example.com, to list its pages.
engineNoShow one engine only, such as chatgpt; omit for every engine.
from_atNoTrends only, required there: start of the window.
audit_idNoOverview or sources: a run id (audit_id); omit for the latest run.
competitorNoOverview or trends: a competitor exactly as the rankings name it, to highlight.
project_idYesA project id that list_projects returned.
snapshot_idNoSite Health only: a snapshot id; omit for the latest crawl.
transport_modelNoTrends only: keep only runs answered by this model.
retrieval_enabledNoTrends only: true keeps runs with web search on, false runs without it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / audit_id / description
      Added value: +"Overview or sources: a run id (audit_id); omit for the latest run."
    • addedInput schema / properties / cohort / description
      Added value: +"core is the scored prompts (the default); comparison is reported separately."
    • addedInput schema / properties / competitor / description
      Added value: +"Overview or trends: a competitor exactly as the rankings name it, to highlight."
    • addedInput schema / properties / cursor / description
      Added value: +"Sources only: the next_cursor a previous page returned."
    • addedInput schema / properties / domain / description
      Added value: +"Sources only: a cited domain such as example.com, to list its pages."
    • addedInput schema / properties / engine / description
      Added value: +"Show one engine only, such as chatgpt; omit for every engine."
    • addedInput schema / properties / from_at / description
      Added value: +"Trends only, required there: start of the window."
    • addedInput schema / properties / level / description
      Added value: +"Sources only: domain lists publishers (the default); url lists pages."
    • addedInput schema / properties / limit / description
      Added value: +"Sources only: rows per page."
    • addedInput schema / properties / project_id / description
      Added value: +"A project id that list_projects returned."
    • addedInput schema / properties / retrieval_enabled / description
      Added value: +"Trends only: true keeps runs with web search on, false runs without it."
    • changedInput schema / properties / retrieval_enabled / type
      Previous value: -[
-  "boolean",
-  "null"
-]New value: +"boolean"
    • addedInput schema / properties / snapshot_id / description
      Added value: +"Site Health only: a snapshot id; omit for the latest crawl."
    • addedInput schema / properties / to_at / description
      Added value: +"Trends only, required there: end of the window."
    • addedInput schema / properties / transport_model / description
      Added value: +"Trends only: keep only runs answered by this model."
    • addedInput schema / properties / view / description
      Added value: +"Which view to show; each other field says the views it applies to."
  2. Changed1 schema field changed
    • changedInput schema / properties / cohort / enum
      Previous value: -[
-  "core",
-  "comparison"
-]New value: +[
+  "core",
+  "comparison",
+  "all"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: this tool renders UI and only functions in app-capable clients, and it is the display counterpart to the read_* tools. It stops short of describing what each view renders or any failure behavior.

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 filler, and the core action plus routing guidance are front-loaded. Every clause earns its place.

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 15-parameter render tool with no output schema, the description covers the essentials: it works only in app-capable clients, which views exist, and when to prefer the read_* alternatives. What each view actually shows is left implicit, which is the only meaningful gap.

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%, so the schema already documents all 15 parameters including the per-view applicability notes. The description's phrase 'trends over a window, or cited sources for one run' only loosely maps to view/from_at/to_at/audit_id and adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 ('Show the user an interactive visibility view') and enumerates the three variants (overview, trends, cited sources). It explicitly distinguishes itself from the read_* siblings by framing this as a display action rather than a data-retrieval one.

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?

Gives an explicit when-to-use condition ('in clients that display apps') and names the three alternatives ('use read_visibility_overview, read_visibility_trends or read_visibility_sources') with the selecting rationale ('To reason over the numbers yourself'). An agent can route correctly without opening any schema.

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

All CiteLadder toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources