Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

find_keyword_opportunities

Discover keyword ideas from seed terms, pages, or competitor domains with search volume, competition, and bids, filtered to content gaps you don't yet rank for.

Instructions

Keyword ideas from a keyword research run started in the app (seed keywords, a page or a competitor domain), with Google Ads search volume, competition and bids next to your own Search Console presence. By default it keeps the content gap: the ideas you don't rank for 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": "find_keyword_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load, and it does disclose the data source, the metric columns merged in, and a default filtering behavior that materially changes results (content gap only). It does not reveal pagination, result limits, or — critically — how the relevant research run is identified given the tool exposes no parameters.

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?

Two sentences, front-loaded with purpose and followed by output/detail and default behavior — no filler. The opening clause is somewhat run-on ('Keyword ideas from a keyword research run started in the app (seed keywords, a page or a competitor domain)'), but everything stated earns its place.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must carry the definition, and it does explain what comes back. What it omits — how the research run is chosen with zero parameters, result volume, and pagination — matters for correct invocation of a tool whose input surface is entirely empty.

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?

The tool takes zero parameters so there is no schema semantics to enrich, and the description cannot document parameters that don't exist. However, because the output depends on an app-side 'run' with no parameter to select it, the description leaves real ambiguity about scope instead of resolving it.

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 names the resource (keyword ideas/opportunities) and its provenance (a keyword research run seeded by keywords, a page, or a competitor domain), and enumerates the fields returned (Google Ads volume, competition, bids, Search Console presence). It is clearly not get_keyword_detail or list_keyword_clusters, though it never states that distinction explicitly or uses a crisp leading verb like 'Return'.

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?

The prerequisite is implied ('a keyword research run started in the app') and the default filter is spelled out ('By default it keeps the content gap'), which implies when the output is useful. But there is no explicit when-to-use vs. alternatives guidance and no statement of when the default filtering is undesirable or how to turn it off.

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