--deprecated

This connector has been deprecated

Replaced by io.github.no-fait/infinite-audience

Get Audience Demographics

get_audience_demographics

Profile a saved audience composition, including its segment set logic and exclusions. Returns a BigQuery-computed demographic breakdown, including median age, gender split, homeowner %, children %, college-educated %, and high-income %. Results may populate a 20-minute server-side cache and record query telemetry; the audience definition is unchanged. Requires 'discovery' scope.

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": {
      "audience_id": "<audience_id>"
    },
    "name": "get_audience_demographics"
  }
}

Input Schema

Name	Required	Description	Default
`audience_id`	Yes	The audience ID to retrieve demographics for

Output Schema

Name	Required	Description
`guidance`	No	Interpretation or recovery guidance for this result
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`audience_id`	Yes
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`extra_field`	No
`total_count`	Yes
`generated_at`	Yes	ISO timestamp of the demographic snapshot
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`age_breakdown`	Yes
`audience_name`	Yes
`geo_breakdown`	Yes
`breakdown_extra`	No
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "age_breakdown": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "audience_id": {
+      "type": "string"
+    },
+    "audience_name": {
+      "type": "string"
+    },
+    "breakdown_extra": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count_state": {
+      "description": "Unknown means no count; available does not guarantee freshness. Recount for a current value.",
+      "enum": [
+        "unknown",
+        "available"
+      ],
+      "type": "string"
+    },
+    "count_unit": {
+      "const": "records",
+      "type": "string"
+    },
+    "extra_field": {
+      "type": "string"
+    },
+    "generated_at": {
+      "description": "ISO timestamp of the demographic snapshot",
+      "type": "string"
+    },
+    "geo_breakdown": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "guidance": {
+      "description": "Interpretation or recovery guidance for this result",
+      "type": "string"
+    },
+    "next_actions": {
+      "description": "Suggested next calls using returned IDs and available scopes. Not executed and not user consent.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "arguments": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "reason": {
+            "type": "string"
+          },
+          "tool": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "arguments",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page_count": {
+      "description": "Number of objects on this page, not the organization total",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "population_input": {
+      "additionalProperties": {},
+      "description": "Population input used for the preview; IDs refer to their current saved definitions",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "total_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_count",
+    "age_breakdown",
+    "geo_breakdown",
+    "generated_at",
+    "audience_id",
+    "audience_name"
+  ],
+  "type": "object"
+}

First observedSep 24, 2026

TDQS

A3.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important side effects: results may populate a 20-minute server-side cache and record query telemetry, while the audience definition remains unchanged. This clarifies why readOnlyHint is false and idempotentHint is false without contradicting destructiveHint=false.

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?

The description is front-loaded with the core action and return content, then adds cache, telemetry, immutability, and scope details compactly. The metric list is long but all items are relevant to the returned demographic breakdown, so no sentence is wasted.

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?

For a one-parameter tool with an output schema and rich annotations, the definition gives enough context about purpose, return contents, side effects, and scope requirements. The main missing piece is explicit guidance on when to use this tool instead of nearby audience or segment demographic tools.

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?

There is only one parameter and schema description coverage is 100%, so the schema already fully documents audience_id. The description does not add format, source, or validation details beyond identifying that demographics are for the saved audience, which is the baseline expectation for a fully documented single parameter.

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 clearly states a specific action and resource: profiling a saved audience composition and returning a demographic breakdown. It implicitly separates itself from segment-oriented siblings by specifying 'saved audience,' but it does not explicitly distinguish itself from tools like get_segment_demographics or get_audience.

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?

The description explains what the tool does and notes a required 'discovery' scope, but it gives no explicit when-to-use guidance or alternatives. It does not tell an agent when to choose this over get_segment_demographics, get_audience, discovery_count, or other audience/segment analysis tools.

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

All --deprecated 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?