Skip to main content
Glama
Sign In
keyword-steroids-gold

keyword-steroids-gold

by MaximKonovalovDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gold_gsc_verify

Verifies if a site URL is confirmed in Google Search Console using the GSC API. Returns verification status to ensure authorized access for SEO workflows.

Instructions

GSC verify — checks site_url verification via GSC API (requires GSC_OAUTH_JSON). Steal: serpfire/gsc-mcp-server 11 stars. PAID ONLY PRO $29. Fail-closed without GSC_OAUTH_JSON.

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": {
      "site_url": "<site_url>"
    },
    "name": "gold_gsc_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYesGSC site_url, e.g. https://example.com/ or sc-domain:example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral disclosure burden and does disclose meaningful traits: the GSC_OAUTH_JSON prerequisite, paid-only access, and fail-closed behavior when credentials are missing. It does not describe the return shape or side effects, but the failure mode and authentication gate are valuable context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and prerequisite are front-loaded, but the description includes extraneous provenance and pricing noise such as 'Steal: serpfire/gsc-mcp-server 11 stars' and 'PAID ONLY PRO $29'. These do not help an agent select or invoke the tool correctly.

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 one-parameter verification tool, the description covers the core purpose, the required credential, and the failure mode. However, with no output schema, it leaves the return value unspecified and does not fully clarify what 'verification' returns or whether any side effects occur.

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 input schema already documents the single site_url parameter with a description and examples, so the description adds little new parameter-level meaning. Schema coverage is 100%, so the baseline of 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 description clearly states that the tool checks site_url verification via the GSC API, giving a specific verb, resource, and scope. It is easily distinguishable from siblings like gold_gsc_insights, though it does not explicitly name an alternative.

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 provides important usage context such as requiring GSC_OAUTH_JSON and failing closed without it, plus the paid-only restriction. However, it does not explicitly say when to prefer this tool over related sibling tools or when not to use it.

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