Skip to main content
Glama

SEO opportunities

find_opportunities
Read-only

Use for best opportunities across quick wins, research ideas, competitor gaps, rank drops, and AI Overview citation gaps. Filter with kinds when the user names one of those.

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_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNo
limitNo
projectIdNo

Output Schema

NameRequiredDescriptionDefault
actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / actions / items / properties / difficulty
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / actions / items / properties / searchVolume
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / actions / items / required
      Previous value: -[
      -  "actionKey",
      -  "type",
      -  "title",
      -  "why",
      -  "estimatedMonthlyClicks",
      -  "effort",
      -  "nextSteps",
      -  "projectId",
      -  "projectName",
      -  "keywordId",
      -  "keyword"
      -]New value: +[
      +  "actionKey",
      +  "type",
      +  "title",
      +  "why",
      +  "estimatedMonthlyClicks",
      +  "searchVolume",
      +  "difficulty",
      +  "effort",
      +  "nextSteps",
      +  "projectId",
      +  "projectName",
      +  "keywordId",
      +  "keyword"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are "best opportunities" (i.e., ranked/prioritized), which is useful context beyond annotations, but says nothing about ranking criteria, limits, or per-project behavior.

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 tight sentences with the primary use case front-loaded and the parameter rule second. Minimal waste; the only friction is that the prose category names don't map cleanly onto the enum values like `ai_visibility`.

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?

An output schema exists, so return values needn't be described. However, for a 3-parameter tool with zero schema descriptions, the omission of projectId scoping and limit defaults leaves real gaps an agent would need to guess at.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only indirectly explains `kinds` (as category filters) and leaves `limit` and `projectId` completely unexplained — notably no hint that projectId scopes the search or what happens when it's omitted.

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?

Names a specific resource (opportunities) and enumerates the five opportunity categories, which concretely describes the output domain. It's clear this is an aggregate/ranked-opportunity tool, though it never explicitly contrasts itself with siblings like find_quick_wins or get_ai_visibility that cover individual categories.

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?

"Filter with kinds when the user names one of those" is a real usage rule for the parameter, but there is no guidance on when to pick this tool over find_quick_wins or get_ai_visibility, nor any prerequisite or exclusion stated.

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