Skip to main content
Glama

List opportunity backlog

opportunities.list

Lists persisted grow and Google Search Console opportunities by source and status (found, approved, shipped, or snoozed) so teams can review and manage SEO/AEO improvement work.

Instructions

Pro: list persisted grow/GSC opportunities (found|approved|shipped|snoozed). Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE.

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": "opportunities.list"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
sourceNo
statusNo
apiBaseUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add genuinely useful context: the data is persisted (not live-fetched), it is gated behind a "Pro" tier, and credentials come from QUALITYKIT_API_KEY + QUALITYKIT_API_BASE. It stops short of saying this is a non-mutating read, whether results are paginated or sorted, or what happens when credentials are absent.

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 short sentences, front-loaded with the action and scope, with no filler. The terse "Pro:" prefix is slightly cryptic but costs almost nothing.

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

Completeness2/5

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

No annotations, no output schema, and zero schema description coverage on a 4-parameter tool means the description is the only explanatory layer, and it covers only status values and credentials. An agent still lacks the source-filter semantics, defaults, and result shape needed to invoke this confidently.

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% across 4 parameters, so the description must compensate. It explains the credential path (env vars mapping to apiKey/apiBaseUrl) and reproduces the status values, but omits the "all" status sentinel and says nothing about the source parameter's grow/gsc/both/all choices or defaults.

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?

"List persisted grow/GSC opportunities" gives a specific verb and resource, and the parenthetical enumerates the status values, so the agent knows this is a read of a stored backlog rather than a sync or update. It does not explicitly contrast itself with opportunities.sync or opportunities.update, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus opportunities.sync (which presumably generates the records) or opportunities.update (which changes status). The status list implies a filtering use case but never says to call this first to discover IDs before updating, nor any exclusion.

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