supermetrics

data_source_discovery

Read-onlyIdempotent

Discover data sources or get a source's configuration. Without ds_id: lists all sources with auth status; data-out-capable sources carry data_out: true (can receive activated audiences), others omit it. With ds_id: returns config (capabilities, report_types, settings, login link if needed). With filter: narrows the list; single match returns full config automatically.

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

Input Schema

Name	Required	Description
`ds_id`	No	When provided, returns full config for this source. Omit to list all.
`filter`	No	Case-insensitive filter against ID, name, categories (e.g. 'ads,social')
`compress`	No	Always recommended. Encodes response as compact text, reducing size and token usage.

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.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavior beyond them: auth status appears in list results, data_out is conditionally present only for capable sources, and login link is included when needed. It does not discuss rate limits or pagination, but for a read-only discovery call this is solid added context.

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?

Four short lines, front-loaded with the core purpose and then organized by mode, with each clause carrying a distinct fact (auth status, data_out conditional, login link, filter auto-expansion). Nothing is redundant or padded.

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 return-value detail is not required, yet the description still summarizes what each mode returns, which is appropriate for a tool with three distinct response shapes. The only omission is any mention of the compress parameter's role in shaping the response.

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?

Schema coverage is 100%, so baseline is 3; the description still adds meaning beyond the schema by spelling out the auto-expand rule (a single filter match returns full config automatically), which the schema does not state. The compress parameter is left unaddressed in the description, relying entirely on the schema's 'Always recommended' note.

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?

The description gives a specific verb+resource ('Discover data sources', 'get a source's configuration') and breaks the tool into three distinct operating modes keyed on ds_id and filter. It never names a sibling such as data_query or accounts_discovery to contrast against, so it stops short of full differentiation.

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?

It explicitly states the condition that selects each mode: omit ds_id to list, pass ds_id for config, pass filter to narrow. That is clear when-to-use guidance for the tool's own parameters, but it offers no when-not-use guidance and no pointer to sibling tools for adjacent tasks.

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?