Skip to main content
Glama
flin-microsoft-ads-mcp

flin-microsoft-ads-mcp

by flin-agency

list_accounts

Read-only

Retrieve accessible Microsoft Advertising accounts, including account IDs and parent customer IDs, and follow paging to browse results.

Instructions

Discover accessible accounts, including account Id and ParentCustomerId. Follow next_page_index.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNo
page_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful return-shape information (account Id, ParentCustomerId) that annotations cannot convey, but it says nothing about auth requirements or result size limits, and it references "next_page_index" without explaining it.

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?

Two short sentences with the resource and return fields front-loaded; no filler. Slightly under-specified rather than bloated, so concision is not the problem.

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 two-parameter read-only discovery tool with no output schema, the essentials are mostly present, but the unresolved page_index vs next_page_index relationship and the unstated auth prerequisite leave real gaps for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does not: page_size (with its 1-1000 bounds and default) and page_index are never explained. Worse, it names "next_page_index", which is not a parameter in the schema, leaving the agent to guess whether pagination is driven by page_index or by a cursor returned in the response.

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?

"Discover accessible accounts" gives a specific verb plus resource, and the mention of account Id and ParentCustomerId clarifies what is returned. It is clearly distinct from the auth/ads/campaigns siblings, though it never explicitly says so.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. whether authentication must be established first via get_auth_url or auth_status), and no exclusions. Only a weak implication that this is the entry point for obtaining account identifiers.

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