Skip to main content
Glama
Sign In
adwhiz-mcp

adwhiz-mcp

by DEXUN-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List connected ad accounts

list_ad_accounts
Read-only

Retrieve all advertising accounts connected to DEXUN AdWhiz, showing platform, name, and connection status. Use to see available accounts for follow-up queries.

Instructions

List every advertising account the user has connected to DEXUN AdWhiz. Returns one row per account with platform (google_ads / meta_ads / tiktok_ads), human-readable name, and connection status. Use this when the user asks 'what accounts do I have' or wants to refer to one of their accounts by name in a follow-up question.

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": "list_ad_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces the read-only nature by stating it only lists accounts, adding no contradictory behavior.

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?

The description is concise and direct, using two sentences to convey purpose, output fields, and usage triggers without unnecessary detail.

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

Completeness4/5

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

While there is no output schema, the description enumerates the returned fields (platform, name, status). This is sufficient for an agent to understand what the tool returns, though a formal schema would be more complete.

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

Parameters4/5

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

The tool has no parameters, so no parameter-specific documentation is needed. The description correctly implies that no arguments are required.

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 clearly states the tool lists connected ad accounts, specifying the returned fields (platform, name, status). It is distinct from sibling tools like list_recommendations or get_savings_summary.

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

Usage Guidelines5/5

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

Explicitly indicates when to use it: when the user asks 'what accounts do I have' or wants to refer to an account by name. This provides clear usage context and differentiation from the other listed tools.

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