Opus Growth, Ad Platforms MCP Connector

Google Ads Accounts

list_accounts

Read-only

Lists the user's connected Google Ads account(s). Returns only the account(s) the user selected at connect time; the response carries default_account_id. all_accessible=true returns every account the credential can reach, which also expands client accounts under MCC (manager) accounts. platform is optional and defaults to Google Ads; naming another connected platform (meta | tiktok | linkedin | microsoft | ga4 | search_console | youtube | business_profile) returns the name of that platform's own account-listing tool instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`platform`	No
`all_accessible`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026
- addedInput schema / properties / platform
```
Added value: +{
+  "default": "",
+  "type": "string"
+}
```
First observedSep 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark the tool readOnly and non-destructive; the description adds the key behavioral facts beyond that: the response carries default_account_id, all_accessible expands under MCC, and platform has a default-and-redirect behavior. No contradiction with 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?

Every clause earns its place: core purpose, default scope, the all_accessible toggle, and platform routing are each specified once with no filler. Information is front-loaded, with the most essential behavior first.

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?

The definition fully equips an agent to call the tool correctly: both parameters are semantically covered, output schema supplies return shape, and annotations supply safety/open-world context. Nothing needed for invocation is missing, and the cross-platform routing prevents misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description carries the full burden for both parameters. It explains platform's optional/default nature, enumerates accepted platform values, and clarifies all_accessible=false/true semantics, including MCC client expansion.

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?

The description opens with a specific verb and resource: 'Lists the user's connected Google Ads account(s).' It immediately distinguishes scoped behavior (connected/selected accounts) from all_accessible behavior, and clarifies that naming a different platform redirects to that platform's own tool, so an agent can tell it apart from list_entities and platform-specific 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?

It gives clear usage context: default returns only accounts selected at connect time, while all_accessible=true expands to all reachable accounts, including MCC clients. It also explains how to delegate to another platform's account-listing tool, though it does not name sibling tools explicitly or include when-not-to-use exclusions.

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

All Opus Growth, Ad Platforms MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.