Skip to main content
Glama
Sign In
Reddit Ads MCP Server

Reddit Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List hosted tools

list_hosted_tools
Read-onlyIdempotent

Lists the hosted Reddit Ads MCP server's available tools with one-line summaries so you can see what an agent can do after connecting, such as create campaigns, pull reports, or upload media.

Instructions

List the tools of the hosted Reddit Ads MCP server by AdKit (https://mcp.adkit.so/reddit-ads), with one line on what each tool does. Use this to explain what an agent can do with ad accounts after connecting, such as creating campaigns, pulling performance or uploading media. Returns a Markdown table. It does not call those tools; they only run on the hosted server.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_hosted_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds value: it discloses the return format (Markdown table) and a non-obvious behavioral fact — that this does not proxy or invoke the listed tools, which only run on the remote server. That last clause prevents an agent from assuming this tool can execute ad operations.

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 sentences, front-loaded with the verb and scope, followed by the use case and then the return-format/behavioral caveat. The inline URL is mildly noisy but justified as the source of the tool listing; nothing is redundant enough to cut.

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 zero-parameter discovery tool with no output schema, the description supplies the missing return-format information (Markdown table) and the critical boundary that it does not invoke the hosted tools. Nothing an agent needs in order to call it correctly is absent.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is required and instead spends its words on output shape and semantics, which is the right allocation of effort for a parameterless tool.

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 ('List the tools of the hosted Reddit Ads MCP server'), names the server and URL, and specifies the granularity ('one line on what each tool does'). An agent can immediately tell this is a discovery/meta tool rather than an ad-account operation, which cleanly separates it from siblings like get_setup_guide or list_ad_platforms.

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?

Gives an explicit use case: 'Use this to explain what an agent can do with ad accounts after connecting,' and enumerates example capabilities (creating campaigns, pulling performance, uploading media). It stops short of naming exclusion conditions (e.g., 'do not use this if you already know the tool names'), so it is clear context without explicit alternatives.

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