Skip to main content
Glama

QualityKit grow impressions

qualitykit.grow

Score Search Console queries against your Site Profile to surface top growth opportunities and deprioritised demand, then get safe or approval-based fixes.

Instructions

Brand-aligned growth: score Search Console queries against the Site Profile, return top opportunities and deprioritised demand, with safe vs approval fixes. Uses Cloud GSC + profile when API key is set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectRoot": "<projectRoot>"
    },
    "name": "qualitykit.grow"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoOptional Pro API key (or QUALITYKIT_API_KEY) for GSC enrichment
siteUrlNo
apiBaseUrlNoOptional QualityKit Cloud base (or QUALITYKIT_API_BASE) to enrich with Search Console
projectRootYesAbsolute path to the website repository root
continueDespiteStaleProfileNoWhen true, allow new-page recommendations even if brand/ICP/products are stale (user explicitly continues).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses dependency on Cloud GSC/profile and that results are categorized as safe vs approval fixes, but never states whether the tool writes anything, what permissions are required, whether fixes are applied or only recommended, or how stale-profile behavior works.

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 compact sentences front-load purpose and then the cloud dependency. 'Brand-aligned growth' is slightly promotional, but the rest is dense and free of repetition.

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?

For a five-parameter analysis tool with no annotations and no output schema, the description is thin on operational behavior and return structure. It gives enough to know the broad job but not enough to call it safely or interpret outputs beyond the headline categories.

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 coverage is 80%, so structured fields already explain most parameters. The description only indirectly references apiKey ('when API key is set') and adds nothing on siteUrl, apiBaseUrl, projectRoot, or continueDespiteStaleProfile; baseline 3 applies.

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 definition names a concrete operation: score Search Console queries against the Site Profile and return top opportunities and deprioritised demand with safe vs approval fixes. It is more specific than the title and defines the output categories, though it does not explicitly contrast with siblings like qualitykit.plan or opportunities.*.

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 implies the tool is for brand-aligned growth analysis using GSC/profile data and states the API-key condition, but gives no explicit when-to-use versus alternatives or when-not guidance.

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