Skip to main content
Glama
camlowe

mcp-server-reddit-ads

get_ads

Read-only

List ads in a Reddit Ads account, filtered by status or ad group. Returns ad records for analysis, excluding creative copy.

Instructions

List ads in an account, optionally filtered to one ad group. Returns ad records only, not creative copy: use get_ad_creative for headline and body text, or compare_ads to rank one ad group's ads by spend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoClient-side filter on configured_status.
account_idNoAd account id. Falls back to REDDIT_ADS_ACCOUNT_ID.
ad_group_idNoOnly return ads in this ad group.
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description correctly aligns. It adds that the tool returns ad records only, not creative copy, but does not disclose additional behavioral traits like pagination or rate limits. The description adds marginal value beyond annotations.

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?

Two sentences with no wasted words. The main purpose is front-loaded, and the additional guidance is compact yet informative.

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?

Given the tool is a list function with optional filters and no output schema, the description adequately covers what it does and points to related tools. Could mention pagination or ordering, but the completeness is sufficient for the complexity.

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 100%, so the parameters are already well-described. The description reinforces the scope (account and ad group) but does not add new meaning beyond what the schema provides. The alternative tool references are not directly parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List ads in an account, optionally filtered to one ad group' with a specific verb and resource. It distinguishes from siblings by noting it returns ad records only, not creative copy, and directs to get_ad_creative and compare_ads for other needs.

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

Usage Guidelines4/5

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

Explicitly mentions when to use get_ad_creative (for creative copy) and compare_ads (to rank ads by spend), providing clear alternatives. Does not explicitly state when not to use this tool, but the guidance is sufficient for an agent to decide.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/camlowe/mcp-server-reddit-ads'

If you have feedback or need assistance with the MCP directory API, please join our Discord server