Skip to main content
Glama

AdLoop

by com.getadloop
OverviewDiscussionsAdmin

Reddit account change history

get_reddit_account_history
Read-only

Who changed what in the Reddit ad account: field, before/after, member, time.

Returns the changes, most recent first, with changed_at, by, entity type, id and name, field, and before/after values. The first thing to check when performance moves. Child entities are included when filtering by entity. Changes made through AdLoop show under the connected Reddit user, like changes made in Ads Manager. Money fields are in account currency.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of changes returned, clamped to 1-500.
entity_idsNoIds of the entities of entity_type to filter to; required when entity_type is set.
entity_typeNoOptional filter to one entity type: "campaign", "ad_group" or "ad". Requires entity_ids.
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 (default window is the last 30 days).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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 / 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 (default window is the last\n30 days)."
    • addedInput schema / properties / entity_ids / description
      Added value: +"Ids of the entities of entity_type to filter to; required\nwhen entity_type is set."
    • addedInput schema / properties / entity_type / description
      Added value: +"Optional filter to one entity type: \"campaign\",\n\"ad_group\" or \"ad\". Requires entity_ids."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of changes returned, clamped to 1-500."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond that: results are most-recent-first, child entities are included when filtering by entity, AdLoop-made changes are attributed to the connected Reddit user, and money fields are in account currency.

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?

Front-loaded with the purpose in the first sentence, and the API link is a useful pointer. There is minor redundancy: the opening phrase lists "field, before/after, member, time" and the next sentence re-lists those same fields, which is wasted text given an output schema already exists.

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, return values need not be re-explained, and the description still covers filtering behavior, currency, attribution quirks, and default windows. Nothing essential for correct invocation is missing, though it never explicitly routes to a sibling history tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning on top of the schema, notably that child entities are pulled in when filtering by entity and that monetary values follow account currency, which shapes how entity_type/entity_ids results should be read.

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 and resource ("Who changed what in the Reddit ad account: field, before/after, member, time") and enumerates the returned fields. The "Reddit ad account" scoping clearly distinguishes it from the sibling get_change_history, which covers a different platform.

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 first thing to check when performance moves" gives a clear triggering context for reaching for this tool. It stops short of naming an alternative or stating exclusions, so it is a solid context statement rather than full when/when-not guidance.

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