reddit_ads_list_languagesList all languages available for targeting in Reddit Ads to find the right audience for your campaigns.
List languages for targeting.
| Name | Required | Description | Default |
|---|---|---|---|
| max_pages | No | Follow pagination.next_url up to this many pages and merge results (default 1) | |
| page_size | No | Items per page (usually max 1000) | |
| page_token | No | Page token from a previous pagination.next_url |
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 no behavioral context beyond that, such as rate limits, pagination behavior, or whether results are cached.
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?
The description is a single efficient sentence with the purpose front-loaded and no wasted words. It is appropriately concise and readable, though very terse.
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 list tool with a fully documented schema and read-only annotations, the description is adequate for invocation. It omits usage guidance and any behavioral context, but the structured fields cover most operational needs.
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 description coverage is 100%, so all three pagination parameters are fully documented in the schema. The description adds no parameter meaning beyond what the schema already provides, which is the baseline 3 for high-coverage schemas.
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 states a clear verb ('List') and resource ('languages'), with the targeting context. It does not explicitly differentiate from the many sibling list_* tools, though 'languages' is unique enough that an agent can distinguish it.
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?
The description gives no when-to-use guidance, prerequisites, or alternatives. 'For targeting' implies a context but does not say when to select this tool over list_time_zones, list_interests, or other targeting list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.