Skip to main content
Glama

Metadata MCP Connector

Create Reddit Target Group

create_reddit_target_group

Create a new Reddit target group with name and targeting criteria (communities, interests, keywords, location).

PREREQUISITE: All references MUST come from search_reddit_criteria. estimate_target_group with channel="REDDIT" first is MANDATORY: verify isMatchCountTooSmall=false and report the reach to the user BEFORE creating. Same bar as create_target_group and update_target_group (PRD-31759). Reddit estimation went live with PRD-31996; before it there was no way to size one of these, which is why a Reddit target group could be created at zero reach with nothing noticing.

USE FOR: "create a Reddit target group named X targeting r/technology", "save this Reddit audience as X".

WARNING: CHANNEL: Only use this tool when the user explicitly asked for a REDDIT target group. Do NOT infer REDDIT from the underlying audience NAMES (e.g. an audience called "Reddit Conquest Mktg LI_n7q" does NOT mean the user wants a REDDIT target group — audience naming is human convention, not a routing signal). Default to create_target_group (LINKEDIN) when channel is unspecified; ask the user if unsure.

TARGETING STRUCTURE (LOCATION must be the FIRST include block with isModifiable=false): { "include": [ { "isModifiable": false, "criteria": [{"type": "LOCATION", "data": { "countries": [229], "states": [] }}], "audiences": [] }, { "isModifiable": true, "criteria": [{"type": "COMMUNITIES", "data": [ {"externalId": "t5_2qh1i", "name": "r/technology"} ]}], "audiences": [] } ], "exclude": { "isModifiable": true, "criteria": [{"type": "KEYWORDS", "data": [{"externalId": "kw_123", "name": "crypto"}]}], "audiences": [] } }

REDDIT CRITERIA TYPES (all references from search_reddit_criteria):

  • LOCATION: {"countries": [, ...], "states": [, ...]} — arrays of NUMERIC Metadata IDs (use the numeric id from search_reddit_criteria locations, NOT the {id, name} object). MANDATORY FIRST in include, isModifiable=false

  • COMMUNITIES: Array of {externalId, name} — subreddits (e.g. r/technology)

  • INTERESTS: Array of {externalId, name} — Reddit interest categories

  • KEYWORDS: Array of {externalId, name} — contextual keywords

INCLUDE: Array of rule blocks (AND-joined). EXCLUDE: single object with criteria and audiences.

AUDIENCES (combine with the criteria above to build complex target groups): each include block and the exclude object also accept an audiences array, so you can mix existing Metadata audiences with the Reddit criteria in the same block. Get them from the audience listing tools / get_matched_audiences. Each audience entry: {mdAudienceId, name, type, matchCount, matchCountType: "FIXED_SIZE", inactive, criteria: [the audience's own criteria]}. mdAudienceId MUST be the numeric Custom Audience ID (integer, e.g. 49067): the customAudienceId / mdAudienceId field of a get_matched_audiences row, NEVER that row's id (the channel row id) and NEVER the audience name string; the platform's mdAudienceId is typed Long, the tool rejects non-integer values pre-flight, and it resolves every id on the platform before the write so a wrong id, an archived audience or one with no live segment on the channel is refused with the reason instead of a "too small" error. In the exclude block, use the EXCLUDE variant of the type (e.g. RETARGETING_EXCLUDE).

RESPONSE: {id, name, channel, audienceSize, status, createdDate, targeting}

WORKFLOW: search_reddit_criteria → build targeting (LOCATION first) → confirm → create_reddit_target_group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name for the new Reddit target group. Must be unique, descriptive, and UNDER 50 characters — the platform rejects 50+ character names with a 400.
targetingYesComplete Reddit targeting configuration with include/exclude rules. LOCATION must be the first include block. All references must come from search_reddit_criteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=false (a write) and destructiveHint=false (non-destructive). The description adds substantial behavioral context beyond these: the mandatory estimation prerequisite and its failure mode (zero reach created without notice), name validation (50+ char rejection with 400), ID resolution behavior (platform resolves ids and rejects non-integers pre-flight), and the fact that wrong/archived audience ids produce a refused reason instead of a 'too small' error. It also clarifies the tool mutates system state by creating a target group. This is rich, non-contradictory disclosure.

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?

The description is long but highly structured with labeled sections (PREREQUISITE, USE FOR, WARNING, TARGETING STRUCTURE, REDDIT CRITERIA TYPES, AUDIENCES, RESPONSE, WORKFLOW). Every section adds necessary information for a complex tool; there is no filler. While it could be tightened, the density and organization justify its length. The front-loading is good—purpose and prerequisites come first. Slightly long for a 1-5, but it earns its place, so 4.

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?

The tool has nested objects with no output schema, and the description covers all aspects: a full targeting example, criteria type definitions, audience mixing, response format, workflow ordering, and prerequisite checks. Given the complexity (2 params but deep nesting) and the absence of an output schema, the description is complete—nothing an agent needs to call it correctly is missing. The workflow list even ties it to sibling search_reddit_criteria and estimate_target_group.

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

Parameters5/5

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

Schema coverage is 100% for the two parameters (name and targeting), so baseline is 3. The description dramatically enhances understanding: it explains the targeting structure with a full JSON example, mandates LOCATION as the first include block with isModifiable=false, details each criteria type (LOCATION, COMMUNITIES, INTERESTS, KEYWORDS) with precise data formats, explains the audiences array and the critical mdAudienceId requirement (numeric custom audience ID, never the row id or name string). This goes far beyond the schema's generic property descriptions, so score 5.

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?

The description opens with a clear verb and resource: 'Create a new Reddit target group with name and targeting criteria (communities, interests, keywords, location).' It distinguishes the tool from siblings by explicitly stating this is Reddit-specific and later warning to default to create_target_group (LinkedIn) when channel is unspecified. The purpose is unambiguous and differentiates from the many other create_* tools.

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?

The description provides explicit when-to-use and when-not-to-use guidance: a 'USE FOR' section gives concrete example utterances, and a 'WARNING' section states 'Only use this tool when the user explicitly asked for a REDDIT target group' and 'Default to create_target_group (LINKEDIN) when channel is unspecified; ask the user if unsure.' It also mandates a prerequisite: call estimate_target_group with channel='REDDIT' and verify isMatchCountTooSmall=false. This is comprehensive routing guidance with exclusions and alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources