Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

OpenAI Ads account

openai_ads_account
Read-onlyIdempotent

Retrieve an OpenAI Ads account ID, name, status, currency, and timezone from a client key; use it to verify the connection before fetching insights.

Instructions

OpenAI Ads (ChatGPT ads) ad account of the client's key (GET /v1/ad_account): only id, name, status, currency_code (the account currency), timezone when present; every other key is dropped and listed in raw_fields_dropped. Use it as a connection test before openai_ads_insights. Cached 300 s ("cached": true). With a registry, refused (account_mismatch) when the key answers for another account than the client's.

Input Schema

NameRequiredDescriptionDefault
client_idNoClient id from clients_list; empty uses the only client (or the environment variables without a 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; empty uses the only client (or the environment variables without a registry)",
+  "title": "Client Id"
+}
  2. Addedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the 300 s cache, the field-dropping behavior with raw_fields_dropped, and the account_mismatch refusal under a registry. These are concrete runtime traits the agent cannot get from the annotations alone.

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?

The value (returned fields) is front-loaded, followed by usage, caching, and refusal notes in compact clauses. Dense but each clause earns its place; could be marginally tightened.

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?

Although there is no output schema, the description enumerates the returned fields and their conditional presence (timezone when present), plus caching and failure modes. Combined with annotations covering the safety profile, nothing needed to call it correctly is missing.

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 the single client_id parameter is fully documented in the schema, so the description need not repeat it. The description adds no parameter syntax or format detail beyond what the schema provides, matching the baseline 3.

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 resource (the OpenAI Ads ad account) and enumerates exactly what it returns: id, name, status, currency_code, timezone. It also clarifies its distinct role versus openai_ads_insights, so an agent can separate it from the other openai_ads_* siblings.

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?

'Use it as a connection test before openai_ads_insights' gives explicit when-to-use and names the natural follow-up tool. The account_mismatch refusal condition further signals when it won't work, though it stops short of stating when this tool is not the right choice.

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