Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server status

server_status
Read-onlyIdempotent

Check configured Google services and OAuth token status for the server or client. Call this first when another tool returns not_configured or not_authenticated.

Instructions

Which Google services are configured for this server (or for one client), and whether the stored OAuth token works. Call it first when another tool answers not_configured or not_authenticated. Returns one boolean per service, the token storage (os-keyring or file), "token": "ok" or the error, and the package version.

Input Schema

NameRequiredDescriptionDefault
client_idNoClient id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / client_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Client id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)",
+  "title": "Client Id"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description goes further by disclosing the return payload: one boolean per service, the token storage backend (os-keyring or file), token 'ok' or the error, and the package version. It does not mention auth/permission prerequisites, but the added output detail is genuine context beyond the annotations.

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

Conciseness5/5

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

Three tight sentences: purpose first, then the trigger condition, then the return shape. Every sentence carries distinct information and nothing is repeated from the name or title.

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

Completeness5/5

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

No output schema exists, but the description enumerates what is returned, and with a single optional parameter fully documented in the schema and annotations covering the safety profile, an agent has everything needed to call it correctly.

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 description coverage is 100% and client_id is fully documented in the schema itself (required when several clients are registered, empty falls back to the only client or env vars). The description only gestures at this with '(or for one client)', adding little beyond structured data. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific diagnostic purpose: which Google services are configured for the server or a single client, plus whether the stored OAuth token works. This is clearly distinguishable from the many action/report siblings (ga4_report, meta_insights, gads_query), which all operate on resources rather than server configuration.

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, actionable trigger: 'Call it first when another tool answers not_configured or not_authenticated.' That is stronger than implied usage. It stops short of naming or contrasting an alternative (e.g. client_check, clients_list), so it is clear context without explicit exclusions.

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