Skip to main content
Glama
Sign In

CiteLadder

by com.citeladder
OverviewDiscussionsAdmin

Read search performance

read_performance
Read-onlyIdempotent

Read the site's organic search performance from Search Console and GA4: clicks, impressions, CTR, average position, sessions and key events for a window, with a series over time and an optional comparison window. Without dimension it returns totals, the series, data coverage and how many rows each breakdown has; with dimension it returns one page of rows by query, page, country, device or day (10 by default, pass next_cursor for more). The range defaults to last_synced, all imported data; most custom windows have no saved snapshot and return performance_range_not_projected, so prefer the preset ranges. not_connected means no search source is connected, which is not zero; read_integration_status says why. Use read_query_evidence for queries matched to crawled pages, and read_ai_referrals for traffic from AI assistants.

Input Schema

NameRequiredDescriptionDefault
sortNoWith dimension: one of clicks, ctr, dimension_key, impressions, position; prefix - for descending, such as -clicks.
limitNoWith dimension: rows per page.
rangeNoThe reporting window.
cursorNoThe next_cursor a previous page returned.
compareNoThe window to compare against; custom needs the compare dates.
end_dateNoLast day of a custom window, inclusive.
dimensionNoBreak the totals down by this dimension, paged.
project_idYesA project id that list_projects returned.
start_dateNoFirst day of a custom window, inclusive.
granularityNoThe bucket size of the totals over time.
compare_end_dateNoLast day of a custom comparison window, inclusive.
compare_start_dateNoFirst day of a custom comparison window, inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedInput schema / properties / compare / description
      Added value: +"The window to compare against; custom needs the compare dates."
    • addedInput schema / properties / compare_end_date / description
      Added value: +"Last day of a custom comparison window, inclusive."
    • addedInput schema / properties / compare_start_date / description
      Added value: +"First day of a custom comparison window, inclusive."
    • addedInput schema / properties / cursor / description
      Added value: +"The next_cursor a previous page returned."
    • changedInput schema / properties / cursor / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • addedInput schema / properties / dimension / description
      Added value: +"Break the totals down by this dimension, paged."
    • addedInput schema / properties / end_date / description
      Added value: +"Last day of a custom window, inclusive."
    • addedInput schema / properties / granularity / description
      Added value: +"The bucket size of the totals over time."
    • addedInput schema / properties / limit / description
      Added value: +"With dimension: rows per page."
    • addedInput schema / properties / project_id / description
      Added value: +"A project id that list_projects returned."
    • addedInput schema / properties / range / description
      Added value: +"The reporting window."
    • addedInput schema / properties / sort / description
      Added value: +"With dimension: one of clicks, ctr, dimension_key, impressions, position; prefix - for descending, such as -clicks."
    • changedInput schema / properties / sort / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
    • addedInput schema / properties / start_date / description
      Added value: +"First day of a custom window, inclusive."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior on top: the default window (last_synced, all imported data), the performance_range_not_projected failure mode, the crucial semantic that not_connected means no source is connected rather than zero, and the 10-row page default with next_cursor continuation. It stops short of explaining how compare/granularity interact with the returned series, which keeps it off 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?

Front-loaded with purpose and return shape, then defaults, then failure modes, then sibling routing — every sentence carries information. It is a dense single paragraph of roughly five sentences; a short bulleted split of return-shape vs. error semantics would scan faster, but nothing here is padding.

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

Completeness5/5

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

With 12 parameters, no output schema, and no nested objects, the description supplies what the schema cannot: the return structure (totals, series, data coverage, row counts per breakdown), paging defaults, the default window, and two named error states with their interpretations. An agent has everything needed to call this correctly and interpret failure responses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the conditional semantics of dimension (totals+series when absent, one page of rows when present), the concrete default of 10 rows, and that next_cursor continues paging. Sorting, comparison dates, and granularity defaults are left to the schema.

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 (read organic search performance) and enumerates the exact metrics returned (clicks, impressions, CTR, average position, sessions, key events) plus the two output shapes (totals+series vs. paged rows by dimension). It also names what it is not, routing the agent to read_query_evidence and read_ai_referrals, so it is distinguishable from siblings without opening a schema.

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?

Explicit conditions are given: use preset ranges because most custom windows have no saved snapshot, use read_query_evidence for queries matched to crawled pages, and read_ai_referrals for AI-assistant traffic. Both alternatives are named with the condition that selects them, which is the strongest form of routing guidance.

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