Skip to main content
Glama

ADS Beast

microsoft_ads_account_setup

Read-only

UET tags, conversion goals and account details of a client's Microsoft Ads account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>"
    },
    "name": "microsoft_ads_account_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered, but the description adds nothing on behavior: no indication of what is returned, whether live API calls are made, or permission requirements. The word 'setup' in the title even hints at mutation, which the description does nothing to resolve against the read-only annotation.

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

Conciseness3/5

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

It is short and wastes no words, but it is a sentence fragment lacking a verb, so there is no front-loaded statement of action. Brevity here reflects under-specification rather than discipline.

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

Completeness2/5

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

For a tool with no output schema and an undocumented parameter, the description should say what resources are returned and how client_id is used; it does neither. The account-setup ambiguity versus read-only annotation remains unresolved.

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?

Only the phrase 'of a client's' hints that client_id selects the account; with schema description coverage at 0%, the description does not compensate by explaining what the identifier is, where to obtain it, or whether it is required. One required parameter is left effectively undocumented in both structured and natural-language form.

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

Purpose2/5

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

The description is a noun phrase listing resources ('UET tags, conversion goals and account details') with no action verb, so it never says whether the tool fetches or configures them. It largely restates the title 'Microsoft Ads account setup' and does not distinguish itself from sibling setups like linkedin_ads_account_setup beyond the platform name.

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 guidance on when to use this tool rather than a sibling such as audit_account or audit_google_ads, nor any stated precondition beyond the implicit client scope. An agent must guess the use case from the title alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.