Skip to main content
Glama
Sign In
Reddit Ads MCP Server

Reddit Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Get step-by-step instructions to connect a supported AI app to the hosted Reddit Ads MCP server by AdKit, including the exact menu path, command, or config snippet.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted Reddit Ads MCP server by AdKit at https://mcp.adkit.so/reddit-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful context beyond that by disclosing the return format (Markdown with exact menu path, command, or config snippet), though it says nothing about what happens for unsupported apps or error cases, which for a static-guide tool is a minor gap.

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

Conciseness5/5

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

Three tight sentences: purpose first, trigger condition second, negative routing to a sibling last. Every sentence carries distinct information and nothing is redundant.

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

Completeness5/5

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

For a one-parameter read-only lookup with no output schema, the definition covers purpose, trigger, alternative, and return format. There is no meaningful gap an agent would need to close before calling it correctly.

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 coverage is 100% and the single 'app' parameter carries a full enum of allowed values with its own description, so the schema does the heavy lifting. The description only lightly reinforces this by saying 'one AI app' and 'in a specific app', adding a hint of single-app-per-call semantics but no format or matching detail beyond the schema.

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: retrieve step-by-step instructions to connect one AI app to the hosted Reddit Ads MCP server by AdKit, including the endpoint URL. This is clearly distinguishable from siblings like list_hosted_tools, which is explicitly named as covering a different need.

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

Usage Guidelines5/5

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

Gives an explicit trigger (user asks how to install, add or connect AdKit in a specific app) and names the alternative for the adjacent case: 'For what the hosted server can do once connected, use list_hosted_tools instead.' No inference required.

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