Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get creative asset

reddit_ads_get_creative_asset
Read-only

Retrieve a Reddit Ads creative asset by its ID to inspect the image or video files linked to your campaigns.

Instructions

Get a creative asset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "creative_asset_id": "<creative_asset_id>"
    },
    "name": "reddit_ads_get_creative_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
creative_asset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

Does 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 nothing beyond that—no note on what the asset payload contains, whether ids are global or account-scoped, or any error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short but that is under-specification rather than conciseness—it conveys no information beyond the title, so the brevity does not earn its place.

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

Completeness2/5

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

With no output schema and no parameter documentation, the description would need to carry the load, but it says nothing about return values, id source, or usage context. Inadequate for even a simple single-parameter retrieval tool.

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

Parameters1/5

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

There is one required parameter (creative_asset_id) with 0% schema description coverage, and the description provides no information about its format, origin, or where to obtain it. The description fails to compensate for the schema gap.

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

Purpose2/5

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

"Get a creative asset" simply restates the tool name and title with no added specificity. It does not distinguish this fetch-by-id tool from siblings like reddit_ads_list_creative_assets, reddit_ads_get_creative_asset_upload, or reddit_ads_update_creative_asset.

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 guidance, no prerequisites, and no mention of alternatives. The agent must infer that this retrieves a single asset by id versus the list variant.

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

Deploy Server

Other Tools