reddit_ads_get_custom_audienceRetrieve a Reddit Ads custom audience by ID to view its status and size, so you can verify it before using it in targeting.
Get a custom audience including its status and size.
| Name | Required | Description | Default |
|---|---|---|---|
| audience_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the response includes status and size, which is useful since there is no output schema, but it says nothing about auth requirements, error conditions (e.g. invalid audience_id), or ownership scoping.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the key noun and the returned fields come first. Nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only lookup with one parameter, the description is minimally adequate and even hints at the return payload. It stops short of explaining how to obtain audience_id or what a failed lookup yields, which an agent would need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter audience_id has 0% schema description coverage and the description never mentions it, so there is no indication of its format, source, or whether it is the numeric Reddit ID or a prefixed string. With low coverage the description was expected to compensate and does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('custom audience') and even names the fields returned (status and size). It is clearly distinct from reddit_ads_list_custom_audiences, create/delete/update siblings by virtue of the singular retrieval, though it never explicitly contrasts itself with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus reddit_ads_list_custom_audiences or the other custom-audience siblings, and no prerequisites or context are given. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.