audiences_getRetrieve a single audience by ID along with its linked resources, so you can inspect audience details and relationships in Advernue before managing campaigns.
Get one audience with its links (GET /v1/audiences/{id}).
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, and the '(GET /v1/audiences/{id})' suffix only reinforces that read-only nature. The description adds no context beyond annotations: it doesn't say what 'links' contains, what happens on a missing audience, or whether related expansions are included.
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 the verb and resource first and the endpoint appended. Nothing is wasted, though the raw endpoint reference is of limited value to an agent that cannot call HTTP directly.
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 one-parameter read tool with no output schema, the definition is nearly sufficient: it names the record fetched and its links, and annotations cover the safety profile. What's missing is any description of the returned audience/links shape, which matters somewhat since no output schema exists.
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?
Schema coverage is 0% for the single required 'id' parameter, so the description must compensate. The path template '{id}' does establish that the parameter is an audience identifier, but it gives no format, source, or example beyond that minimal hint.
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?
The description uses a specific verb and resource ('Get one audience') and scopes it to a single record, which implicitly distinguishes it from audiences_list. The added 'with its links' signals extra payload, though what 'links' means is never explained.
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?
Usage is only implied: fetch a single audience by id. It never names audiences_list as the alternative for browsing, nor says when a detail fetch is preferable to list, and gives no preconditions such as requiring a known id.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.