Skip to main content
Glama
GlobalMatchHub

SearchLink Lite

by GlobalMatchHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find opportunities

find_opportunities
Read-onlyIdempotent

Identifies quick SEO wins: high-impression low-click queries, rankings #8-20, and declining clicks, with suggested fixes.

Instructions

Finds the quickest wins: queries seen often but rarely clicked (rewrite the title or description), queries ranking #8 to #20 (one push from page one), and pages losing clicks. Use when the user asks what to improve or where to start. Returns each item with its numbers and the suggested fix. 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 items per kind of opportunity, 1 to 50. Default 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • 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."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items per kind of opportunity, 1 to 50. Default 15."
    • 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."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds behavioral depth by explaining the selection logic and return contents (numbers and suggested fixes), going beyond the annotation-only picture.

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 compact: it front-loads the outcome, then gives the trigger condition, return shape, and safety hint. Every sentence earns its place with no filler or redundancy.

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 the fully documented schema, rich non-destructive annotations, and a clear return-shape statement, nothing an agent needs to invoke this tool correctly is missing. The absence of an output schema is compensated by the explicit mention of returned numbers and suggested fixes.

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%, with all three parameters (days, site, limit) fully documented in the input schema. The description itself adds no parameter-specific semantics, so the baseline of 3 is appropriate.

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 names a specific verb ('Finds') and resource ('opportunities'), then enumerates three concrete opportunity categories. This makes its purpose unambiguous and clearly distinguishes it from siblings like search_performance or site_overview.

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?

It explicitly states when to use the tool: 'Use when the user asks what to improve or where to start.' This is clear and actionable, though it does not name specific alternatives or exclusion conditions.

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

Deploy Server

Other Tools