Reddit Ads MCP server

reddit get lead form

reddit_get_lead_form

Read-onlyIdempotent

Read a Reddit lead form and confirm it belongs to your ad account; returns form configuration only, never lead submissions.

Instructions

Read one Reddit lead form and verify that it belongs to the ad account. Form configuration only; lead submissions are never returned.

Input Schema

Name	Required	Description	Default
`id`	Yes	ID of the Reddit lead form to read. It must belong to adAccountId.
`adAccountId`	Yes	Reddit ad account ID (a2_...) listed in REDDIT_ADS_ACCOUNT_IDS, not the business ID.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive operation, so the description does not need to restate safety. It adds real behavioral value by clarifying the return boundary: 'Form configuration only; lead submissions are never returned,' and by noting that it verifies ad-account ownership.

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?

Two tightly written sentences with no filler. The key differentiator ('one') and the most important output boundary ('lead submissions are never returned') are front-loaded.

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

Completeness4/5

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

Given an output schema and full parameter coverage, the description covers the essential scope and output boundary an agent needs. It stops short of describing failure behavior when the form does not exist or does not belong to the ad account, but otherwise it is complete.

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%, so both parameters are already fully documented, including patterns and the requirement that id belongs to adAccountId. The description reinforces the cross-parameter ownership constraint but does not add format or validation details 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 ('Read one Reddit lead form') and immediately scopes it against the sibling list tool by saying 'one'. The ownership-verification clause and the 'form configuration only' boundary further sharpen what is being fetched.

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

Usage Guidelines3/5

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

The phrase 'Read one' implies this tool is for single-form retrieval rather than listing, and the ownership check implies a valid adAccountId/id pair is required. However, no alternative tools are named and there is no explicit when-to-use/when-not-to-use guidance beyond what the reader infers from 'one'.

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