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

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get SKAdNetwork availability

reddit_ads_get_skan_availability
Read-only

Check SKAdNetwork campaign, ad group, and ad quota availability for an iOS app in Reddit Ads.

Instructions

Get SKAdNetwork campaign, ad group and ad quota for an iOS app.

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": {
      "app_id": "<app_id>"
    },
    "name": "reddit_ads_get_skan_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
ad_group_idNo
campaign_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
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 safety profile is covered. The description adds the iOS scope and the three categories of returned data (campaign, ad group, quota), which is modestly useful, but it says nothing about auth requirements, rate limits, or the meaning of 'quota'.

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 no filler. It is efficient, though its brevity is partly a symptom of under-specification rather than disciplined concision.

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, 0% parameter coverage, and three parameters, the description leaves the agent without parameter semantics or any sense of the return shape. It is too thin for the complexity of the call despite the annotations covering safety.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters, so the description must carry the burden, yet it never names app_id, ad_group_id, or campaign_id. It loosely gestures at 'campaign' and 'ad group' but gives no format, required/optional distinction, or scoping semantics.

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?

The description states a specific verb ('Get') and resource ('SKAdNetwork campaign, ad group and ad quota'), and no sibling tool overlaps with SKAdNetwork, so it is distinguishable. It is slightly fuzzy on what 'availability' concretely resolves to, but the scope (iOS app) is clear.

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?

There is no guidance on when to call this versus alternatives, prerequisites, or the condition that makes SKAdNetwork availability relevant. The agent is told what the tool returns but not when it is the right choice.

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