Skip to main content
Glama

Searches your site almost wins

search_positions

The Google searches this site ranks in the top 20 for (US), from an index of Google results that is refreshed every few weeks: targets are the ones at 4 to 20, most searched first, each with its page, monthly searches and difficulty; changes is what moved since the last check. Lift one target per PR on the page that already ranks. Costs $0.10 from the balance, charged only when it returns. Nothing is charged when the site ranks for nothing yet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the index refresh cadence, US scope, and a precise cost model ($0.10 charged only when results are returned, nothing charged when the site ranks for nothing). It does not contradict the annotations.

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?

The description is front-loaded and dense with useful information, with no obvious filler. The backtick field references and cost details are efficient, though the first sentence is long and could be easier to scan.

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 no output schema and no parameters, the description does a good job explaining what is returned, how fresh the data is, and the cost model. It could be slightly more complete about the structure of `changes`, but it is sufficient for an agent to call the tool correctly.

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?

There are zero input parameters, so the baseline is 4. The description instead explains the returned `targets` and `changes` fields, which adds useful meaning even though it is not input-parameter semantics.

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 clearly identifies the resource: Google searches where the site ranks in the top 20 in the US, with `targets` at positions 4–20 and `changes` since the last check. It is specific and distinguishable, but it does not explicitly contrast itself with sibling tools such as app_ranks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives actionable guidance on what to do with the results — lift one target per PR on the page that already ranks — but does not state when to use this tool versus alternatives or when not to use it.

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