Skip to main content
Glama

TrueClicks

by com.trueclicks

Users' My Accounts selections

user_my_accounts
Read-only

Get each user's selected 'My Accounts' as JSONL, one row per user-account selection. My Accounts is the set of accounts a user has picked as their own in TrueClicks (a per-user preference, not an access-permission list). Filter by accountIds to limit to specific accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdsNoOptional TrueClicks account ids to limit the result to (the numeric Id field from the account listing). Omit to return all accounts.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / accountIds / description
      Previous value: -"Optional account IDs to limit the result to. Omit to return all accounts."New value: +"Optional TrueClicks account ids to limit the result to (the numeric Id field from the account listing). Omit to return all accounts."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate read-only, and description adds no extra behavioral details but clarifies output format (JSONL).

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?

Two sentences with no redundancy, all information relevant.

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?

Explains the concept of My Accounts, the output format (JSONL, one row per selection), and the optional filter; sufficient despite lack of output schema.

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 fully describes accountIds with optionality and meaning; description only repeats the filter behavior, so no additional meaning beyond schema.

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 verb ('Get') and resource ('each user's selected My Accounts'), distinguishes from sibling tools like 'account' and 'user' by clarifying it's a per-user preference, not access-permission.

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?

Provides context on when to use (when you need user preferences, not permissions) and mentions optional filtering by accountIds, but does not explicitly name alternative tools for comparison.

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

All TrueClicks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the audit and report tools (e.g., audit_rule_output_table vs audit_rule_output_table_historical vs audit_rule_result vs audit_rule_result_campaign) are closely related and rely on detailed descriptions to differentiate.

Naming Consistency4/5

Naming is generally consistent with snake_case and domain-prefixed groups (google_ads_*, ms_ads_*, perfmon_*), though a few tools are bare nouns (account, task, user) rather than verb-led, which slightly deviates from the dominant pattern.

Tool Count4/5

23 tools is on the higher end but justified for a platform covering multiple ad platforms, audit reports, alerts, and user management; it remains navigable with clear groupings.

Completeness4/5

The tool set comprehensively covers account enumeration, audit results, report execution for major ad platforms, perfmon alerts, pacing targets, tasks, and users. Minor gaps exist (e.g., no create/update/modify operations), but the core analytics and monitoring surface is well covered.

Resources