Skip to main content
Glama
get-mcp-ads

Reddit Ads MCP server

reddit get profiles

reddit_get_profiles
Read-onlyIdempotent

List Reddit ad profiles accessible to a specified ad account, with pagination via cursor and limit controls for retrieving profiles.

Instructions

List profiles accessible to the allowed Reddit ad account.

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1 to 100. Defaults to 50.
cursorNoOpaque next_cursor returned by the previous page. Omit it for the first page.
adAccountIdYesReddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds the useful scoping fact that results are limited to profiles accessible to the allowed ad account, but says nothing about pagination behavior or return shape.

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?

A single front-loaded sentence with zero waste. It is perhaps too terse for the scope it needs to convey, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations relieve some burden, but the description never clarifies what a 'profile' is in Reddit Ads terms or how it relates to targeting/audiences, which matters in a sibling set this dense.

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 description coverage is 100% (limit, cursor, adAccountId all documented including the a2_ prefix and cursor opacity), so baseline 3 applies. The description adds no parameter-level meaning beyond the schema.

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?

Clear verb+resource: lists profiles scoped to an ad account. The resource (profiles) is distinct from every sibling (campaigns, ads, audiences, pixels, etc.), though the description never explicitly contrasts with them.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative routing. An agent knows what the tool returns but not under what circumstances to prefer it over, say, reddit_get_targeting or reddit_get_custom_audiences.

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