Skip to main content
Glama
GlobalMatchHub

SearchLink Lite

Search performance (custom)

search_performance
Read-onlyIdempotent

Generate custom Search Console reports grouping by query, page, country, device, or date; filter and sort data, then compare against the previous period to reveal performance changes.

Instructions

Custom Search Console report when site_overview is not specific enough: group by query, page, country, device or date (up to two at once), filter by query or page text, sort, and optionally add the change against the previous period. Returns a table with clicks, impressions, CTR and position per row. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLength of the period in days, 7 to 480, ending about 3 days ago because Google data lags. It is compared with the same number of days right before it. Default 28.
siteYesThe Search Console property to read. Accepts "example.com", "https://example.com/" or "sc-domain:example.com". Call list_sites first if unsure which properties exist.
limitNoMaximum rows to return, 1 to 200. Default 25.
sort_byNoWhich number to sort rows by, highest first (position: best first). Default clicks.clicks
group_byNoOne or two dimensions to break the numbers down by, e.g. ["query"] or ["page", "query"]. Default ["query"].
filter_pageNoKeep only pages whose URL contains this text, e.g. "/blog/".
filter_queryNoKeep only search queries that contain this text (case-insensitive), e.g. a brand or product name.
compare_previousNoAdd each row's change against the previous period of the same length. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.2.0
    • addedInput schema / properties / compare_previous / description
      Added value: +"Add each row's change against the previous period of the same length. Default false."
    • changedInput schema / properties / days / description
      Previous value: -"Length of the period in days (compared with the period right before it)."New value: +"Length of the period in days, 7 to 480, ending about 3 days ago because Google data lags. It is compared with the same number of days right before it. Default 28."
    • changedInput schema / properties / filter_page / description
      Previous value: -"Only pages whose URL contains this text."New value: +"Keep only pages whose URL contains this text, e.g. \"/blog/\"."
    • changedInput schema / properties / filter_query / description
      Previous value: -"Only queries containing this text."New value: +"Keep only search queries that contain this text (case-insensitive), e.g. a brand or product name."
    • addedInput schema / properties / group_by / description
      Added value: +"One or two dimensions to break the numbers down by, e.g. [\"query\"] or [\"page\", \"query\"]. Default [\"query\"]."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return, 1 to 200. Default 25."
    • changedInput schema / properties / site / description
      Previous value: -"Your site, e.g. \"example.com\". Use list_sites to see options."New value: +"The Search Console property to read. Accepts \"example.com\", \"https://example.com/\" or \"sc-domain:example.com\". Call list_sites first if unsure which properties exist."
    • addedInput schema / properties / sort_by / description
      Added value: +"Which number to sort rows by, highest first (position: best first). Default clicks."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds the read-only statement and describes the output table shape (clicks, impressions, CTR, position), plus the grouping/filtering/sorting capabilities. It does not contradict annotations and adds useful behavioral context.

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?

The description is three sentences, front-loaded with the purpose and distinguishing condition, then the capabilities and output. There is no filler, repetition, or unnecessary detail.

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?

Given that all 8 parameters are fully documented in the schema and the annotations already cover safety and idempotency, the description provides sufficient top-level context: what the report does, when to use it, and what it returns. Nothing needed for correct selection and invocation is missing.

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% and each parameter already has detailed descriptions. The tool description summarizes the parameter capabilities (group_by, filter_query/page, sort_by, compare_previous) but does not add new semantic information beyond what the schema already provides.

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?

The description states a specific resource (Search Console property) and a clear set of actions: grouping, filtering, sorting, and comparing. It explicitly differentiates from the sibling tool site_overview with 'when site_overview is not specific enough', making its purpose distinct.

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?

The description explicitly names the alternative tool (site_overview) and the condition under which search_performance should be used instead. This gives an agent a clear decision rule for tool selection.

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