Skip to main content
Glama

Mark GSC recommendations applied

visibility.mark_applied

Snapshot Search Console metrics for grow topChanges IDs after fixes and deployment so later visibility.report shows per-change impression deltas.

Instructions

After grow → fix → verify (and deploy), snapshot Search Console metrics for grow topChanges ids so later visibility.report shows per-change impression deltas. Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE. GSC data often lags 1–3 days.

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": "visibility.mark_applied"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoOptional explicit snapshots with path/query from qualitykit.grow topChanges (preferred when ids are grow page ids).
labelNoLabel for this applied change set
apiKeyNoPro API key (or set QUALITYKIT_API_KEY env)
changeIdsNoGrow topChanges / GSC opportunity ids to snapshot. Omit to snapshot all current ranked opportunities.
apiBaseUrlNoQualityKit Cloud API base URL (or set QUALITYKIT_API_BASE).
alsoSiteBaselineNoAlso save a site-wide GSC baseline (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/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 disclose the required credentials (QUALITYKIT_API_KEY + QUALITYKIT_API_BASE) and a useful caveat that GSC data lags 1–3 days. It does not disclose whether re-running overwrites a prior snapshot, whether the operation is idempotent, or what 'applied' marking actually persists, which matters for a write-style tool.

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, front-loaded with the workflow placement before the prerequisites and lag caveat. Minor redundancy in restating the env-var names that also appear as apiKey/apiBaseUrl schema parameters.

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?

For a six-parameter write-style tool with no annotations and no output schema, the definition covers when to call and credentials but omits what the call returns (snapshot handle, label echo, counts) and how repeated invocations behave. Adequate to invoke, thin on expected outcomes.

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 100%, so all six parameters are already documented in the schema, including changeIds, items, and alsoSiteBaseline defaults. The description adds only the 'grow topChanges ids' provenance framing, which the schema already states, so baseline 3 is appropriate.

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?

States a specific verb and resource: 'snapshot Search Console metrics for grow topChanges ids', and ties the result to visibility.report's per-change deltas, which distinguishes it from that sibling. Slight friction remains because the tool name says 'mark_applied' while the description frames the action as snapshotting, leaving the 'marking' semantics implicit.

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

Usage Guidelines4/5

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

Gives an explicit pipeline position: 'After grow → fix → verify (and deploy)', which tells the agent when in the workflow to call it. It does not state any when-not-to-use condition or what to do instead if the pipeline stage was skipped, so it stops short of full routing guidance.

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