supermetrics

accounts_discovery

Read-onlyIdempotent

Discover connected accounts for a data source. Only call if data_source_discovery config shows has_account_list=true. RETURNS: account_id, account_name, group_name (when present), tags (when present), and any saved business context for the account: shown as context when short enough to include, otherwise as context_tags naming what context exists — when a tag is relevant to the action you're taking, fetch that context with get_business_context (ds_id + account_id, filtered by tag).

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": {
      "ds_id": "<ds_id>"
    },
    "name": "accounts_discovery"
  }
}

Input Schema

Name	Required	Description
`ds_id`	Yes	Data source ID from data_source_discovery (e.g. 'FA', 'AW', 'GAWA')
`filter`	No	Case-insensitive filter against account ID, name, group, tags (comma-separated)
`compress`	No	Always recommended. Encodes response as compact text, reducing size and token usage. In tables, an empty cell means not set and list values are \|-joined.

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`notes`	No
`success`	Yes
`business_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely non-obvious behavior: how business context is either inlined as `context` or truncated to `context_tags`, and the follow-up call needed to expand it. It does not mention pagination or result-size limits, which keeps it off a 5.

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?

Front-loads purpose, then the gating condition, then returns — a sensible order with no filler. The RETURNS sentence is long with several nested clauses (field list, context vs context_tags, fetch instruction), which slightly hurts scannability but every clause carries information.

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?

An output schema exists, so the return-field enumeration is partly redundant, but the `context`/`context_tags` truncation nuance and the follow-up fetch path add real completeness. For a simple 3-parameter listing tool the description covers purpose, precondition, return shape and next step; only pagination/size behavior is absent.

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 description coverage is 100%, so `ds_id`, `filter` and `compress` are already documented in the schema, including the compress recommendation and table encoding. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 and resource ("Discover connected accounts") and scopes it to a data source. It also implicitly separates itself from data_source_discovery by making that tool's config the gate, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit call condition: "Only call if data_source_discovery config shows has_account_list=true," which doubles as a when-not-to-call rule. It also routes the agent forward, naming get_business_context with the exact parameters (ds_id + account_id) and tag filter needed to retrieve truncated context.

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

All supermetrics 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.

Resources

Need Help?