Skip to main content
Glama

AdLoop

by com.getadloop
OverviewDiscussionsAdmin

Raw Reddit report

run_reddit_report
Read-only

Run a custom Reddit Ads report for metrics get_reddit_performance omits.

Returns the requested fields per breakdown row, the date range and the account currency. Microcurrency and cent fields are converted to currency amounts.

Queries the Reddit Ads API: https://ads-api.reddit.com/docs/v3/

Input Schema

NameRequiredDescriptionDefault
fieldsYesReddit report field names (required), e.g. ["SPEND", "CLICKS", "REACH", "VIDEO_STARTED", "CONVERSION_PURCHASE_TOTAL_VALUE", "KEY_CONVERSION_TOTAL_COUNT"].
filterNoReddit filter expression (e.g. "campaign_id==abc123"). Empty means no filter.
breakdownsNoUp to 3 of DATE, HOUR, CAMPAIGN_ID, AD_GROUP_ID, AD_ID, COUNTRY, REGION, COMMUNITY, KEYWORD, INTEREST, PLACEMENT, GENDER, OS_TYPE (4 when COUNTRY and REGION are both included; HOUR and DATE cannot be combined).
time_zone_idNoIANA time zone for the day boundaries and DATE/HOUR rows, e.g. "Europe/Berlin". Empty uses the ad account's time zone.
ad_account_idNoReddit ad account id (from list_reddit_accounts). Empty uses reddit.ad_account_id from the config.
date_range_endNoLast day (inclusive), YYYY-MM-DD (account-local day). Empty means today.
date_range_startNoFirst day, YYYY-MM-DD (account-local day). Empty means 29 days before date_range_end (a 30-day window).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / ad_account_id / description
      Added value: +"Reddit ad account id (from list_reddit_accounts).\nEmpty uses reddit.ad_account_id from the config."
    • addedInput schema / properties / breakdowns / description
      Added value: +"Up to 3 of DATE, HOUR, CAMPAIGN_ID, AD_GROUP_ID, AD_ID,\nCOUNTRY, REGION, COMMUNITY, KEYWORD, INTEREST, PLACEMENT, GENDER,\nOS_TYPE (4 when COUNTRY and REGION are both included; HOUR and\nDATE cannot be combined)."
    • addedInput schema / properties / date_range_end / description
      Added value: +"Last day (inclusive), YYYY-MM-DD (account-local day).\nEmpty means today."
    • addedInput schema / properties / date_range_start / description
      Added value: +"First day, YYYY-MM-DD (account-local day). Empty\nmeans 29 days before date_range_end (a 30-day window)."
    • addedInput schema / properties / fields / description
      Added value: +"Reddit report field names (required), e.g. [\"SPEND\",\n\"CLICKS\", \"REACH\", \"VIDEO_STARTED\",\n\"CONVERSION_PURCHASE_TOTAL_VALUE\", \"KEY_CONVERSION_TOTAL_COUNT\"]."
    • addedInput schema / properties / filter / description
      Added value: +"Reddit filter expression (e.g. \"campaign_id==abc123\"). Empty\nmeans no filter."
    • addedInput schema / properties / time_zone_id / description
      Added value: +"IANA time zone for the day boundaries and DATE/HOUR\nrows, e.g. \"Europe/Berlin\". Empty uses the ad account's time zone."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine behavioral context beyond that: it returns requested fields per breakdown row plus date range and account currency, and it normalizes microcurrency/cent values to currency amounts, which materially affects interpretation of results.

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?

Three short sentences, front-loaded with the differentiator, then output behavior, then an API reference link. The doc URL is mildly expendable but genuinely useful for field-name discovery, so structure is tight overall.

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?

With an output schema present, the description need not explain return values, and it still summarizes the return shape and currency conversion. Combined with 100% schema coverage and annotations, an agent has enough to call this correctly; only auth/permission prerequisites are unstated.

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%, so all seven parameters are already documented in the schema with examples, defaults and constraints. The description only echoes 'requested fields' and 'breakdown row' without adding syntax or semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb (Run) and resource (custom Reddit Ads report) and immediately distinguishes itself from the sibling get_reddit_performance by scoping to 'metrics get_reddit_performance omits'. An agent can tell which Reddit reporting tool to pick without opening schemas.

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?

The phrase 'for metrics get_reddit_performance omits' establishes the selection condition relative to a named alternative, which is clear routing guidance. It stops short of an explicit when-not rule or a direct pointer back to get_reddit_performance for standard metrics, so it is not fully prescriptive.

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

All AdLoop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources