User Intuition

List Targeting Attributes

list_targeting_attributes

Read-onlyIdempotent

Search the panel targeting catalog by name or category. Use its qualification and option IDs when configuring a panel study. The full study response also resolves saved targeting to readable labels; age bands can be approximate.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`category`	No
`organization_id`	No	Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Panel qualification and option IDs with readable labels.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed16 schema fields changedSep 30, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / properties / result / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / result / items / properties / category / $ref
```
Removed value: -"#/properties/result/items/properties/name"
```
- addedOutput schema / properties / result / items / properties / category / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / result / items / properties / options / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / result / items / properties / options / items / properties / option_id / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / items / properties / options / items / properties / option_id / minimum
```
Added value: +-9007199254740991
```
- removedOutput schema / properties / result / items / properties / options / items / properties / text / $ref
```
Removed value: -"#/properties/result/items/properties/name"
```
- addedOutput schema / properties / result / items / properties / options / items / properties / text / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / result / items / properties / qualification_id / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / items / properties / qualification_id / minimum
```
Added value: +-9007199254740991
```
- removedOutput schema / properties / result / items / properties / question_text / $ref
```
Removed value: -"#/properties/result/items/properties/name"
```
- addedOutput schema / properties / result / items / properties / question_text / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / items / properties / type / $ref
```
Removed value: -"#/properties/result/items/properties/name"
```
- addedOutput schema / properties / result / items / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds a useful caveat that age bands can be approximate, but its sentence about resolving labels refers to the full study response rather than this tool's output, which is tangential and slightly confusing about what this call returns.

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?

Three short sentences, purpose first, usage second, caveat last; nothing is bloated. The final sentence is somewhat tangential since it concerns study responses rather than this list call.

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 values need no explanation, and annotations cover the read-only safety profile. The main residual gap is filtering behavior (pagination, exact vs partial match) for a search-style tool with three parameters.

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 coverage is only 33%: name and category have no descriptions, and the description partially compensates by implying both are search filters. It does not say whether matching is exact or substring, how the two filters combine, or how they interact with organization_id, so the compensation is incomplete.

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?

States a specific verb and resource ('Search the panel targeting catalog') and scopes it to name or category filters. No sibling tool covers targeting attributes, so additional differentiation isn't needed, but the name/list vs description/search wording is slightly loose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use its qualification and option IDs when configuring a panel study' explains why an agent would call it and what to do with the result, which is useful context. However, it never states when NOT to use it or points to any alternative (e.g., against search_research), so usage is implied rather than explicit.

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

All User Intuition 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?