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

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create lead gen form

reddit_ads_create_lead_gen_form

Create a lead generation form for Reddit Ads to collect prospect emails, phone numbers, or company details using custom questions.

Instructions

Create a lead generation form.

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": {
      "data": "<data>"
    },
    "name": "reddit_ads_create_lead_gen_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesSent as {"data": {...}}. Fields: name, privacy_link (https URL), prompt, questions [{type: EMAIL|FIRST_NAME|LAST_NAME|PHONE_NUMBER|POSTAL_CODE|JOB_TITLE|COMPANY|COMPANY_EMAIL, required}] (at least one required).
ad_account_idNoAd account ID (t2_... or a2_...). Defaults to REDDIT_ADS_ACCOUNT_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the basic safety profile is covered. However, the description adds nothing beyond that: it does not mention required fields, that the form is created in an ad account, any auth requirements, or what the resulting form object looks like. With annotations present the bar is lower, but a mutation tool that adds zero behavioral context lands at a 2.

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?

It is a single short sentence with zero waste, but it is under-specified rather than concise. The one sentence conveys nothing the tool name did not already convey, so brevity here is a deficiency, not a virtue.

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?

This is a creation tool with a nested required object (questions with at least one entry) and no output schema, yet the description explains none of the mandatory shape, the account scoping, or the result. The schema rescues callability, but the prose leaves the agent without any operational context.

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 description coverage is 100% – the nested data object already documents name, privacy_link, prompt, and the questions array with its enum types and constraint. The description adds no parameter meaning on top of that, so the baseline of 3 applies.

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?

"Create a lead generation form" simply restates the tool name and title with no additional specificity. It does not distinguish this tool from its siblings reddit_ads_get_lead_gen_form or reddit_ads_list_lead_gen_forms beyond the obvious verb, nor does it hint at what a lead gen form requires.

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 use this tool, what prerequisites exist (e.g., an ad account or business context), or how it relates to the sibling list/get form tools. The agent must infer usage entirely from the name.

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